Consumer product information request (CPIR) enabling servlets and web-based consumer product information catalogs employing the same

ABSTRACT

A consumer product information requesting (CPIR) enabling Servlet for execution on the server-side of an information network such as the Internet. The CPIR-enabling Servlet comprises a Universal Product Number (UPN) a uniquely associated with a particular consumer product on which an information search is to be carried out within a database management subsystem. One or more classes are loaded on a an Internet-enabled information server. When the consumer selects a CPIR-enabling Servlet tag embedded within the WWW and corresponding CPIR-enabling Servlet, a UPN-directed-search is automatically carried out within the database management subsystem, the a graphical user interface (GUI) is displayed within the Internet-enabled browser program used by the consumer, and the results from the UPN-directed search are displayed within the GUI in the form of a menu of categorized URLs pointing to consumer product related information resources published on the WWW, without disturbing the consumer&#39;s point of presence thereon. The CPIR-enabling Servlets can be used to build various types of consumer product information systems for operation on the WWW.

RELATED CASES

This Application is a Continuation-in-Part of application Ser. No. 09/284,917 which was entered into the U.S. on Apr. 21, 1999 now abandoned which is a National Stage Entry Application from International Application No. PCT/US97/19227 filed Oct. 27, 1997, published as WIPO Publication No. WO 98/19259 on May 7, 1998; as well as a Continuation-in-Part of the following U.S. applications: Ser. No. 08/736,798 filed Oct. 25, 1996, now U.S. Pat. No. 5,918,214; Ser. No. 08/752,136 filed Nov. 19, 1996, now U.S. Pat. No. 6,064,979; Ser. No. 08/826,120 filed Mar. 27, 1997, now abandoned; Ser. No. 08/854,877 filed May 12, 1997 now U.S. Pat. No. 5,950,173; Ser. No. 08/871,815 filed Jun. 9, 1997; and Ser. No. 08/936,375 filed Sep. 24, 1997 now abandoned, each said Application is commonly owned by IPF, Inc., and is incorporated herein by reference in its entirety as if fully set forth herein.

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention generally relates to a novel system and method for collecting consumer-product related information and transmitting and delivering the same along the consumer-product supply and demand chain using the International Information Infrastructure (e.g. the Internet), and more particularly to a novel system and method for delivering consumer product related information to consumers within retail environments using Internet-based information servers and sales agents.

2. Brief Description of the Prior Art

Dissemination of consumer-product information between manufacturers and their retail trading partners must be accurate and timely. The traditional methods of phone calls and faxes are time consuming and resource intensive. An electronic Universal Product Code (UPC) Catalog (i.e. database system), accessible 24 hours a day, is a solution. In 1988, QuickResponse Services (QRS), Inc. Of Richmond, Calif., introduced the first independent product information database, using the retail industry standard UPC numbering system. Today the QRSolutions™ Catalog contains information on over 52 million products from over 1500 manufacturers. The QRSolutions Catalog is a Windows-based application providing a critical information flow link between the retailers and the manufacturers along the supply and demand chain.

After assigning a UPC number to each item, the manufacturer organizes and sends the data via an electronic data interchange (i.e. EDI) transmission, or a tape, to QRS, Inc. to be loaded into the UPC Catalog database. Changes to the data can be made on a daily basis. Retailers with access to a manufacturer's data can view and download the data once it has been added or updated. Automatic update capabilities ensure the most recent UPC data will be in the EDI mailbox of each retailer customer quickly.

The effect of a centralized database such as QRS's UPC Catalog improves the flow of merchandise from the manufacturer to the retailer's selling floor and ultimately to the consumer. With the UPC Catalog, accurate, up-to-date product information is available when the retailer needs it, eliminating weeks from the order cycle time.

In addition to the electronic UPC-based product information subsystem (i.e. UPC Catalog) described above, a number of other information subsystems have been developed for the purpose of providing solutions to problems relating to electronic commerce (EC) merchandising and logistics within the global supply chain. Such ancillary information subsystems include, for example: Sales, Analysis and Forecasting Subsystems for producing and providing retailers with information about what products consumers are buying; Collaborative Replenishment Subsystems for determining what products retailers can buy in order to satisfy consumer demand at any given point of time; and Transportation and Logistics Information Subsystems for producing and providing retailers with information about when products purchased by them (at wholesale) will be delivered to their stores. Typically, such information subsystems are connected to various value added information networks in order to efficiently offer such information services to retailers on a global basis.

While the above-described information systems collectively cooperate to optimize the process of moving raw materials into finished products and into the hands of consumers, such information systems fail to address the information needs of the consumers of retail products who require and desire product-related information prior to, as well as after, the purchase of consumer-products. . Moreover, prior art demand chain management systems operate in an open-loop mode with a “break” in information flow cycle, disabling the manufacturers from communicating with the consumers in an efficient manner to satisfy consumer needs.

Presently, an enormous amount of time, money and effort is being expended by companies in order to advertise and sell their products and services, and to provide product related information, product warranty service and the like after product purchase has taken place. Various types of media for decades have been used to realize such fundamental business functions.

In recent times, there has been a number of significant developments in connection with the global information network called the “Internet”, which has greatly influenced many companies to create multi-media Internet Web-sites in order to advertise, sell and maintain their products and services. Examples of such developments include, for example: the World Wide Web (WWW) based on the Hypertext Markup Language (HTML) and the Hypertext Transmission Protocol (HTTP) by Tim Berners-Lee, et al. (See “World-Wide Web: The Information Universe” by Tim Berners-Lee, et al; easy to use Java GUI-based Internet navigation tools, such as the Netscape® browser from Netscape Communications, Inc., the Internet Explorer™ browser from MicroSoft Corporation and the Mosaic™ browser from Spyglass Corporation; and the Virtual Reality Modeling Language (VRML) by Mark Pecse. Such developments in recent times have made it very easy for businesses to create 2-D Hypermedia-based Home Pages and 3-D VR Worlds (i.e. 3-D Web-sites) for the purpose of projecting a desired “corporate image” and providing a backdrop for financial investment solicitation, as well as product advertising, sales and maintenance operations.

Presently, a person desiring to acquire information about any particular product has a number of available search options. In particular, he or she may attempt to directly contact the manufacturer, wholesaler or reseller by telephone, US mail, e-mail, or through the company's World Wide Web-site (WWW), if they have one. In the event one decides to acquire product information through the seller's WWW site, he or she must first determine the location of its WWW site (i.e. Internet address) which oftentimes can involve using Internet Search engines such as Yahoo®, AltaVista™, WebCrawler™, Lycos™, Excite™, or the like. This can be a very time consuming process and can sometimes lead to a dead end. Once the Internet address is obtained, one must then review the home page of the company's Web-site in order to find where information about a particular product resides on the Website, if it so exists. This search process can be both time consuming and expensive (in terms of Internet time) and may not turn up desired information on the product of interest.

In some instances, product brochures bear a preprinted Internet address designed to direct or point prospective customers to a particular Web-site where more detailed product information can be found. A recent example of this “preprinted Web Address” pointing technique is the 1996 product brochure published by the Sony Corporation for its Sony® PCV-70 Personal Computer, which refers prospective customers to the Sony Web Address “http://www.sony.com/pc”. While this approach provides a direct way of finding product related information on the Internet, it is not without its shortcomings and drawbacks.

In particular, when a company improves, changes or modifies an existing Web-site which publishes product and/or service advertisements and related information, it is difficult (if not impossible) not to change the Internet locations (e.g. Web addresses) at which such product and/or service advertisements and related information appear. Whenever a company decides or is forced to change any of its advertising, marketing and/or public relations firms, there is a substantial likelihood that new Web-sites will be created and launched for particular products and services, and that the Web addresses of such new Web-sites will no longer correspond with the Web addresses on preprinted product brochures currently in circulation at the time. This can result in pointing a consumer to erroneous or vacant Web-sites, that present either old or otherwise outdated product and/or service information, possibly adversely influencing the consumer's purchasing decision.

Moreover, when a company launches a new Web-site as part of a new advertising and marketing campaign for a particular product, any preprinted advertising or marketing material relating to such products will not reflect the new Web-site addresses which the campaign is promoting. This fact about preprinted advertising media renders it difficult to unify new and old advertising media currently in circulation into an advertising and marketing campaign having a coherent theme. In short, the inherently static nature of the “preprinted Web address” pointing technique described above is wholly incapable of adjusting to the dynamic needs of advertising, marketing and public relations firms alike.

Recently, two different methods have been proposed for providing product information to consumers over the Internet.

U.S. Pat. No. 5,640,193 to Wellner discloses a system and method for accessing and displaying Web-based consumer product related information to consumers using a Internet-enabled computer system, whereby in response to reading a URL-encoded bar code symbol on or associated with a product, the information resource specified by the URL is automatically accessed and displayed on the Internet-enabled computer system. While this system and method enables access of consumer product information related information resources on the WWW by reading URL-encoded bar code symbols, it requires that custom URL-encoded bar code symbols be created and applied to each and every consumer product in the stream of commerce.

U.S. Pat. No. 5,978,773 to Hudetz, et al discloses a solution to the problem presented by the system and method of U.S. Pat. No. 5,640,193, by proposing the use of a UPC/URL database in order to translate UPC numbers read from consumer products by a bar code scanner, into the URLs of published information resources on the WWW relating to the UPC-labeled consumer product.

While U.S. Pat. No. 5,978,773 provides an effective solution to the problem presented by U.S. Pat. No. 5,640,193, it completely fails to recognize or otherwise address the myriad of problems relating to UPC/URL-link collection, management, delivery, access and display along the retail supply and demand chain, which the system and method of U.S. Pat. No. 5,978,773 presents and must be first solved in order deliver a technically feasible, globally-extensive, UPC-driven consumer product information system for the benefit of consumers worldwide.

Thus, it is clear that there is great need in the art for an improved Internet-based method of and system for delivering product related information to the consumers along the entire retail supply and demand chain, while avoiding the shortcomings and drawbacks of prior art systems and methodologies.

DISCLOSURE OF THE INVENTION

Accordingly, a primary object of the present invention is to provide a novel method and apparatus for collecting product-related information and transmitting and delivering the same between the manufacturers and retailers of products to the consumers thereof in retail shopping environments as well as at home, work and on the road, while overcoming the shortcomings and drawbacks of prior art systems and methodologies.

Another object of the present invention is to provide such apparatus in the form of a novel consumer-product information collection, transmission and delivery system.

Another object of the present invention is to provide such a system with an Internet-based product information database subsystem which, for each commercially available consumer-product, stores a number of information elements including: the name of the manufacturer; the Universal Product Code (UPC) assigned to the product by the manufacturer; one or more URLs specifying the location of information resources (e.g. Web-pages) on the Internet relating to the UPC-labeled consumer-product; and the like.

Another object of the present invention is to provide such a system, in which the URLs stored in the Internet-based product information database are categorically arranged and displayed according to specific types of product information (e.g., product specifications and operation manuals; product wholesalers and retailers; product advertisements and promotions; product endorsements; product updates and reviews; product warranty/servicing; related or complementary products; product incentives including rebates, discounts and/or coupons; etc.) that relate to the kind of information required, desired or otherwise sought by consumers, wholesalers, retailers and/or trading partners; product prices at which the products are being offered for sale by a particular retailer; and the like.

Another object of the present invention is to provide such a system, wherein the information maintained within the Internet-based product information database management subsystem provides a manufacturer-defined consumer-product directory that can be used by various persons along the retail supply and demand chain.

Another object of the present invention is to provide such a system, wherein the manufacturers of consumer-products are linked to the retailers thereof in the middle of the supply and demand chain by allowing either trading partner to access to consumer-product information from the Internet-based product information database virtually 24 hours a day, seven days a week.

Another object of the present invention is to provide such a system, wherein consumer-product manufacturers, their advertisers, distributors and retailers are linked to the consumers of such products at the end of the supply and demand chain, by allowing such parties access to consumer-product information from the Internet-based product information database subsystem virtually 24 hours a day, seven days a week.

Another object of the present invention is to provide such a system and method of using the same, which will accelerate the acceptance of electronic commerce on the Internet and the development of the electronic marketplace, which can be used by consumers and small and large businesses alike.

Another object of the present invention is to provide a novel system and method for finding and serving consumer-product related information on the Internet.

Another object of the present invention is to provide such a system and method, wherein virtually any type of product can be registered with the system by symbolically linking or relating (i) its preassigned Universal Product Number (e.g. UPC or EAN number) or at least the Manufacture Identification Number (MIN) portion thereof with (ii) the Uniform Resource Locators (URLs) of one or more information resources on the Internet (e.g. the home page of the manufacturer's Web-site) related to such products.

Another object of the present invention is to provide such a system and method wherein a Web-based document transport subsystem is provided for use by manufacturers as well as their advertisers and agents in registering the UPNs (e.g. UPC numbers) of their products and the URLs of the information resources related to such products.

Another object of the present invention is to provide such a system with a number of different modes of operation, namely: a Manufacturer/Product Registration Mode, wherein manufacturers can register their companies and consumer products (e.g. UPC numbers and URLs) with the system; an UPN-Directed Information Access Mode, wherein consumers can access and display information menus containing UPC numbers linked to URLs pointing Web pages containing consumer product related information by scanning the UPC label on the consumer product or by entering the UPC number thereof into a data-entry screen displayed by the system in this mode; a Manufacturer Website Search Mode, wherein the home page of a manufacturer's Web-site can be automatically accessed and displayed by scanning the UPC label on any consumer product of the manufacturer or by entering the UPC number thereof into a data-entry screen displayed by the system in this mode; a Trademark-Directed Search Mode enabling consumers to use trademarks and/or tradenames associated with consumer products to search for consumer-product related information registered within the system; and a Product-Description Directed Search Mode enabling consumers to use product descriptors associated with particular consumer products to search for consumer-product related information registered within the system.

Another object of the present invention is to provide such a system, wherein when the system is in its UPN-Directed Information Menu Access Mode, a predesignated information resource (e.g. advertisement, product information, etc.) pertaining to any commercial product registered with the system can be automatically accessed from the Internet and displayed from the Internet browser by simply entering the registered product's UPN into the Internet browser manually or by bar code symbol scanning.

Another object of the present invention is to provide such a system, wherein when the system is in its Trademark-Directed Search Mode, a predesignated information resource (e.g. advertisement, product information, etc.) pertaining to any commercial product registered with the system can be automatically accessed from the Internet and displayed from the Internet browser by simply entering the registered product's trademark(s) and/or associated company name into the Internet browser.

Another object of the present invention is to provide such a system, wherein when the system is in its Product-Description-Directed Search Mode, a predesignated information resource (e.g. advertisement, product information, etc.) pertaining to any commercial product registered with the system can be automatically accessed from the Internet and displayed from the Internet browser by simply entering the registered product's product description into the Internet browser.

Another object of the present invention is to provide such a system, wherein a predesignated information resource pertaining to any commercial product having been assigned a Universal Product Number (UPN) can be accessed from the Internet and displayed from the Internet browser by simply selecting its and then entering the UPN numeric string into an Input Box which pops up on an HTML form displayed by an Internet browser.

Another object of the present invention is to provide such a system in which a relational database, referred to as “an Internet Product Directory (IPD),” is realized on one or more data-synchronized IPD Servers for the purpose of registering product related information, namely: (i) information representative of commercial product descriptions, the trademarks used in connection therewith, the company names providing and/or promoting such products, the E-mail addresses of such companies, and the corresponding URLs on the Internet specifying current (i.e. up-to-date) Internet Web-site locations providing product-related information customized to such products.

Another object of the present invention is to provide such a product information finding and serving system, wherein the URLs symbolically linked to each registered product in the IPD Servers thereof are categorized as relating primarily to Product Advertisements, Product Specifications, Product Updates, Product Distributors, Product Warranty/Servicing, and/or Product Incentives (e.g. rebates, discounts and/or coupons), and that such URL categories are graphically displayed to the requester by way of easy-to-read display screens during URL selection and Web-site connection.

A further object of the present invention is to provide an Internet-based System wherein: (1) manufacturers and their agents are enabled to simply link (i.e. relate), manage and update within a centralized database, the UPC (and/or UPC/EAN) numbers on their products and the Uniform Resource Locators (URLs) of HTTP-encoded document (i.e. Web pages) containing particular kinds of consumer product-related information published on the Internet by the manufacturers, their agents and/or third parties; and (2) consumers, in retail stores, at home, in the office and on the road, are enabled to simply access such consumer product-related information using such UPC (and/or UPC/EAN) numbers and/or by scanning UPC (or UPC/EAN) bar code symbols encoded with such product identification numbers.

Another object of the present invention is to provide a novel method of carrying out electronic-type commercial transactions involving the purchase of products which are advertised on the Internet at uniform resource locations (URLs) that are registered with the IPI system of the present invention.

Another object of the present invention is to provide a novel system and method of finding the UPN or USN associated with any particular registered product, respectively, by simply selecting a Java GUI button on the Internet browser display screen in order to enter a “Trademark-Directed Search Mode”, whereby (i) a dialogue box is displayed on the display screen requesting any known trademarks associated with the product, and/or the name of the company that makes, sells or distributes the particular product, and (ii) the corresponding UPN (i.e. UPC number or EAN number) registered with the IPD Servers is displayed to the user for acceptance, whereupon the Internet Uniform Resource Locators (URLs) are automatically accessed from the IPD Servers and displayed on the display screen of the Internet browser for subsequent URL selection and Web-site connection.

Another object of the present invention is to provide such a system and method, wherein during the Trademark-Directed Search Mode, the UPN (e.g. UPC or EAN number) associated with any registered product can be found within the database of the IPD Server using any trademark(s) and/or the company name commonly associated with the product.

Another object of the present invention is to provide a novel system and method for serving consumer-product related information to Internet users in retail shopping environments (e.g. department stores, supermarkets, superstores, home-centers and the like) as well as at home, work or on the road.

Another object of the present invention is to provide a consumer product information access terminal located at a point-of-sale (POS) station, wherein the bar code symbol reader integrated with the POS station can be used to read the UPC numbers on consumer products being offered for sale in the store in order to access consumer product related information from hyper-linked Web-sites on the Internet, for display on an LCD screen located at the POS station and viewable from various positions by the sales clerk as well as consumer shoppers.

Another object of the present invention is to provide a system and method, wherein one or more computer-based kiosks are installed within retail shopping environments and each such kiosk has an automatic bar code symbol reader for reading the UPC numbers on consumer products being offered for sale in the store, and also an LCD touch-type display screen for displaying product-related information accessed from hyper-linked Web-sites on the Internet.

Another object of the present invention is to provide such a system and method, wherein one or more computer-based kiosks are installed within retail shopping environments and each such kiosk has an automatic bar code symbol reader for reading the UPC numbers on consumer products being offered for sale in the store, and also a LCD touch-type display screen for displaying product-related information accessed from hyper-linked Web-sites on the Internet.

Another object of the present invention is to provide such a consumer product information kiosk, wherein the laser scanning bar code symbol reader can be easily removed from its support stand to scan large consumer products that might be difficult to present within the scanning field while the bar code symbol reader is supported above the LCD display panel.

Another object of the present invention is to provide such a consumer product information kiosk, wherein the laser scanning bar code symbol reader has a cordless interface with the kiosk so that it may be moved about within a retail store in a portable manner to scan UPC labels and access consumer product related information.

Another object of the present invention is to provide a consumer product information kiosk for use with the system hereof, that is completely transportable within the store by hand, or may be mounted upon a shopping cart or other vehicle for the convenience of shoppers and the like.

Another object of the present invention is to provide “virtual” or “Cyber” sales and service agents within retail shopping environments by installing the computer-based kiosks of the present invention therein.

Another object of the present invention is to provide a Web-based information delivery system and method, wherein the computer-based kiosks employed throughout the hosting retailer's store are capable of displaying the price of products offered for sale in the store upon reading the UPC bar code symbol thereon.

Another object of the present invention is to provide a novel method of constructing a relational database for use within the product information finding and serving subsystem of the present invention.

Another method of the present invention is to provide such a method of database construction, wherein the relational database is initially “seeded” with: (i) the Manufacturer Base UPC Numbers based on the six digit UPC Manufacturer Identification Numbers (MIN) assigned to the manufacturers by the UCC and incorporated into the first six characters of each UPC number applied to the products thereof; and (ii) the URLs of the Web-site home pages of such manufacturers.

Another method of the present invention is to provide such a method of database construction, wherein the “seeded” relational database is then subsequently extended and refined with the participation of each registered manufacturer (and/or agents thereof) by adding to the “seeded” database (iii) the 12 digit UPC numbers assigned to each product sold thereby and the menu of URLs symbolically linked to each such corresponding product.

Another object of the present invention is to provide such a system and method, in which Web-site-based advertising campaigns can be changed, modified and/or transformed in virtually any way imaginable by simply restructuring the symbolic links between the products and/or services in the campaign using current (i.e. up-to-date) Web-site addresses at which Web-site advertisements and information sources related thereto are located on the Internet.

Another object of the present invention is to provide a novel system and method of automatically soliciting companies to register their products within the databases of such IPD Servers in order that product related information of a multimedia nature (e.g. Web-sites), once registered therewith, can be easily found on the Internet by anyone using the system and method of the present invention.

Another object of the present invention is to provide a novel system and method for finding and serving consumer-product related information on the Internet, accessible from the Websites of each manufacturer who has registered its UPN/URLs with the system's “central” IPD Database.

Another object of the present invention is to provide such a system and method, wherein as part of the consumer product registration process, the manufacturer (or retailer) maintains a limited-version of the UPN/URL database which contains a list of categorized URLs for each UPC-encoded product that it sells.

Another object of the present invention is to provide such a system and method, wherein the consumer product related information links contained within the limited-version of the UPN/URL Database of each registered manufacturer (or retailer) can be accessed from the manufacturer's (or retailer's) company Website and served to consumers requesting such information by way of UPC (or EAN) number entry.

Another object of the present invention is to provide such a system and method, wherein input HTML forms for searching the limited-version of the UPN/URL Database of each registered manufacturer (or retailer) can be accessed by selecting a predesignated Check Button on the Java GUI to a Website providing access thereto.

Another object of the present invention is to provide such a system and method, wherein the limited-version of the UPN/URL Database of each registered manufacturer (or retailer) is used to update a “central” or “master” UPN/URL Database which is continuously maintained and made accessible to consumers (i) through Web-based kiosks installed in licensed retail environments and (ii) through Internet-enabled client subsystems located at home, work and school.

Another object of the present invention is to provide such a system and method, wherein at the time of registering each manufacturer (or retailer) with the system, an Internet-based registration server automatically transmits a computer program to the manufacturer's (or retailer's) computer system for use in constructing and maintaining the limited-version UPN/URL Database related to the manufacturer's (retailer's) products.

Another object of the present invention is to provide such a system and method, wherein the limited-version UPN/URL Database of each registered manufacturer (or retailer) can be served from the manufacturer's (or retailer's) Internet information server using a Common Gateway Interface program (CGI).

Another object of the present invention is to provide such a system and method, wherein the limited-version UPN/URL database of each registered manufacturer (or retailer) is realized using a cross-platform compatible, relational database management system (RDBMS).

Another object of the present invention is to provide a novel method of and system for accessing consumer product related information at points within HTML-encoded documents, at which Universal Product Number (UPN) encoded Java Applets are embedded so as to produce, when executed, a consumer product information display enabling (“CPID-enabling”) Java-based graphical user interfaces (GUIs) for the convenience of consumers shopping at electronic-commerce (EC) enabled stores, considering the placement of bids at on-line auction sites, or browsing product advertisements appearing on the World Wide Web.

Another object of the present invention is to provide an Internet-based consumer product information collection, managing and delivery system and method, wherein for each consumer product registered within the UPN/URL database of the system, there is created and stored, an interactive consumer product information request (CPIR) enabling Applet (e.g. based on Java™ component principles or MicroSoft's Active-X technology) which, when executed upon the initiation of the consumer through a mouse-clicking operation, automatically causes a preassigned CPID-enabling Java GUI to be displayed at the consumer's point of presence in Cyberspace, revealing the results of a consumer product information display conducted upon the product identified by the UPN encoded within the executed Applet.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein (1) the UPN assigned to a particular consumer product by the manufacturer and (2) the URL of the Java script running on the IPD server of the system are encoded within the CPIR-enabling Applet so that, upon execution of the Applet, a consumer product information display (CPID) Java GUI is automatically produced for the consumer's convenience.

Another object of the present invention is to provide an Internet-based consumer product information collection, managing and delivery system and method, wherein the CPID-enabling Java GUI automatically displays a manufacturer-defined menu (i.e. list) of categorized URLs pointing to information resources on the Internet (e.g. WWW) relating to the consumer product identified by the UPN encoded within the CPIR-enabling Applet.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein CPIR-enabling Applets are created by the system administrator, loaded within the UPN/URL database management subsystem thereof, distributed to retailers, wholesalers, manufacturers, advertisers and others for embedding within HTML-encoded documents associated with EC-enabled stores, catalogs, Internet-based product advertisements, on-line auction sites, and other locations on the WWW where accurate consumer product related information is desired or required without leaving the point of presence on the WWW at which the consumer resides.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein CPIR-enabling Applets are created, distributed, embedded within a HTML-encoded document related to a particular consumer product, and subsequently executed by a consumer so as to access and display a manufacturer-defined menu (i.e. list) of categorized URLs pointing to product-related Web-documents.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein the consumer initiating the execution of a particular CPIR-enabling Applet may be anyone desiring or requiring consumer product related information while interacting with the communication medium provided by the Internet and its supported technologies (e.g. WWW, EC, etc.). As such, the consumer may be a student shopping at an EC-enabled (business-to-consumer) retail store for textbooks, a retail purchasing agent shopping at an on-line (business-to-business) wholesale product catalog for product inventory, a dealer looking to purchase a new or used product listed at an on-line auction site, or anyone encountering an Internet-based advertisement while surfing the WWW.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein a thumb-nail picture, arbitrary graphical object, predesignated CPIR-indicating icon, or hypertext-type link associated with a particular consumer product can be embedded within the CPIR-enabling Applet associated therewith, so as to enable the consumer to produce a CPID-enabling Java GUI upon encountering the same in an HTML-encoded document on the WWW.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein licensed users can download CPIR-enabling Applets from the CPIR-Enabling Applet Library to any client computer for eventual insertion within the HTML code of a particular Web-document to be published on the Internet in accordance with the licensing arrangement between the contracting parties. Such end-use applications might be in EC-enabled retail product catalogs, EC-enabled wholesale/trade catalogs, Internet-based product advertisements, and the like.

Another object of the present invention is to provide such an Internet-based consumer product information collection, managing and delivery system and method, wherein the CPID-enabling Java GUIs enabled by executed CPIR-enabling Applets can function as CPI-serving “cyber-kiosks” that can be installed at any location in Cyberspace for the convenience of consumers residing therewithin without disturbing their point of presence.

Another object of the present invention is to provide a novel method of and system for delivering consumer product advertisements and consumer product related information to consumers over the WWW involving the use of a single mouse-clicking operation by the consumer.

Another object of the present invention is to provide a novel method of and system for embedding CPIR-enabling Applets within HTML-encoded consumer product advertisements published over the WWW involving the use of a single mouse-clicking operation by the consumer.

Another object of the present invention is to provide a novel method of and system for delivering consumer product related information to consumers at on-line auction sites on the WWW involving the use of a single mouse-clicking operation by the consumer.

Another object of the present invention is to provide a novel method of and system for embedding CPIR-enabling Applets within HTML-encoded on-line auction pages published over the WWW.

Another object of the present invention is to provide a new method of and system for purchasing a consumer product over the Internet (e.g. WWW) comprising the steps of: embedding a UPN-encoded CPIR-enabling Applet within the HTML-code of a consumer product advertisement, wherein the CPIR-enabling Applet when executed displays a categorized URL menu containing one or more URLs pointing to one or more EC-enabled stores or on-line catalogs on the WWW at which the consumer product identified by the encoded UPN can be purchased and delivered to a particular address in physical space.

Another object of the present invention is to provide a novel cyber-kiosk, launchable from predefined points of presence within an EC-enabled store, on-line product catalog or other type of WWW site, for enabling consumers (including retail purchasing agents) to quickly access and display at the predefined point of presence, an interactive menu of categorized URLs pointing to consumer product related information resources published on the WWW and symbolically linked to the UPNs of consumer products within a centralized UPN/URL database management subsystem, by manufacturers and/or their agents.

Another object of the present invention is to provide a novel EC-enabled product catalog having a library of CPIR-enabling Applets embeddable within graphical images of consumer products in HTML-encoded documents and enabling, when executed, a UPN-directed search within the UPN/URL database management subsystem and the display of an interactive menu of categorized URLs pointing to consumer product related information resources published on the WWW and symbolically linked to the UPNs of consumer products within a centralized UPN/URL database management subsystem, by manufacturers and/or their agents.

Another object of the present invention is to provide a novel Internet-based electronic commerce (EC) enabled shopping system comprising an Internet information server connected to the infrastructure of the Internet and supporting the hypertext transmission protocol (http), a Web-enabled client subsystem connected to the infrastructure of the Internet, an EC-enabled WWW site comprising a plurality of interlinked HTML-encoded documents arranged and rendered to provide an electronic store environment when served to a consumer operating the Web-enabled client subsystem, wherein the electronic store environment presents a plurality of products for purchase and sale by an EC-enabled payment method supported over the Internet.

Another object of the present invention is to provide such an Internet-based electronic commerce (EC) enabled shopping system, wherein a Java Applet tag, associated with each product, is embedded within at least one of the HTML-encoded documents displayed on the Web-enabled client subsystem, and each Java Applet tag is associated with a Java Applet encoded with the universal product number (UPN) assigned to one of the products, and, when the consumer selects one of the Java Applet tags, the associated Java Applet is automatically executed enabling a search to be conducted against a product information database hosted on an Internet database server connected to the Internet, from which the results of the UPN-specified search are automatically displayed in a GUI served to the Web-enabled client subsystem.

Another object of the present invention is to provide client-side and server CPIR-enabling Java Applets for enabling the consumer product information searches at virtually any consumer point of presence on the WWW by performing a single mouse-clicking operation.

These and other objects of the present invention will become apparent hereinafter and in the Claims to Invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of how to practice the Objects of the Present Invention, the following Detailed Description of the Illustrative Embodiments can be read in conjunction with the accompanying Drawings, wherein:

FIG. 1 is a schematic diagram illustrating the various information subsystems provided by the consumer-product information collection, transmission and delivery system of invention along the consumer-product demand chain, namely an Internet-based Product-Information (IPI) Finding and Serving Subsystem, a UPC-based Product-Information Subsystem (“UPC Catalog”), an Electronic Trading Information Subsystem, a Sales Analysis and Forecasting Information Subsystem, Collaborative Replenishment Information Subsystem, and a Transportation and Logistics Information Subsystem;

FIGS. 2-1 and 2-2 show a schematic diagram of the consumer-product information collection, transmission and delivery system of the illustrative embodiment hereof shown embedded with the infrastructure of the global computer communications network known as the “Internet”, and comprising a plurality of data-synchronized Internet Product Directory (IPD) Servers connected to the infrastructure of the Internet, a UPN/URL Database Subsystem (i.e. UPN/URL Database) connected to one or more of the IPD Servers and one or more globally-extensive electronic data interchange (EDI) networks, a Web-based Document Server connected to at least one of the IPD Servers and the Internet infrastructure, a Web-based Document Administration Computer connected to the Web-based Document Server by way of a TCP/IP connection, a plurality of manufacturer-related electronic-commerce (EC) information servers for hosting EC-enabled stores or EC-enabled on-line catalogues of manufacturers, a plurality of retailer-related electronic-commerce (EC) information servers for hosting EC-enabled stores or EC-enabled on-line catalogues of retailers, a plurality of Internet Product-Information (IPI) Servers connected to the infrastructure of the Internet for serving consumer-product related information to consumers in retail stores and at home, a plurality of Client Subsystems connected to the infrastructure of the Internet and allowing manufacturers to transmit consumer-product related information to the Web-based Document Server for collection and retransmission to the IPD Servers, and a plurality of Client Subsystems connected to the infrastructure of the Internet and allowing consumers in retail stores and at home to request and receive consumer-product related information from the IPD Servers;

FIG. 2A is a schematic diagram illustrating the flow of information along the consumer-product supply and demand chain, including (i) the communication link extending between the information subsystems of manufacturers of UPC-encoded products and the centralized (or master) UPN/URL Database Management Subsystem 9 of the consumer-product information collection, transmission and delivery system of the present invention, (ii) the communication link extending between the UPN/URL Database Management Subsystem and the IPD Servers of the present invention, (iii) the communication link extending between the IPD Servers and in-store Client Subsystems of retailers, (iv) the communication link extending between the IPI Servers and the in-store Client Subsystems of retailers, (v) the communication link extending between the IPD Servers and the Client Subsystems of consumers, (vi) the communication link extending between the IPI Servers and the Client Subsystems of consumers, and (vii) the communication link extending between the UPN/URL Database Management Subsystem and the EC-enabled UPN-based Consumer Product Catalogue Server(s) of the present invention for providing consumer product catalogue services to retailer purchasing agents and others and enabling the on-line purchase of consumer products between trading partners (e.g. manufactures and retailers) using EDI (or XML/EDI) based business-to-business electronic commerce transactions;

FIG. 2B1 is a block schematic diagram of the IPD Server of the first illustrative embodiment, showing its subsystem components namely a relational database management subsystem (RDBMS) server and a Java Web Server with Java servlet support, being accessed by a Java-enabled client machine seeking to access consumer product related information from the RDBMS server using server-side Java Applets whose HMTL tags are embedded within HTML-encoded documents served to the client machine from any one of a number of potential http information servers on the Internet;

FIG. 2B2 is a block schematic diagram of the IPD Server of the second illustrative embodiment, showing its subsystem components namely a relational database management subsystem (RDBMS) server and a Java Web Server with CGI script support, being accessed by a Java-enabled client machine seeking to access consumer product related information from the RDBMS server using client-side Java Applets whose HTML tags are embedded within HTML-encoded documents served to the client machine from any one of a number of potential http information servers on the Internet;

FIG. 2B3 is a block schematic diagram of the IPD Server of the third illustrative embodiment, showing its subsystem components, namely: a relational database management subsystem (RDBMS) server and a Java Web Server being accessed by a Java-enabled client machine seeking to access consumer product related information from the RDBMS server using (i) a socket connection between the client machine and the Java Web server and (ii) client-side Java Applets whose HMTL tags are embedded within HTML-encoded documents served to the client machine from any one of a number of potential http information servers on the Internet;

FIG. 2B4 is a block schematic diagram of the IPD Server of the fourth illustrative embodiment, showing its subsystem components, namely: a relational database management subsystem (RDBMS) server and a Java Web Server being accessed by a Java-enabled client machine seeking to access consumer product related information from the RDBMS server using (i) a Remote Method of Invocation (RMI) and (ii) client-side Java Applets whose HMTL tags are embedded within HTML-encoded documents served to the client machine from any one of a number of potential http information servers on the Internet;

FIG. 2C is a schematic representation of a portion of the system shown in FIGS. 2-1 and 2-2, wherein a plurality of manufacturer-operated client subsystems are shown connected to a local or wide area IP-based network, preferably maintained behind a secure corporate firewall, and the secured manufacturer information network is connected to the infrastructure of the Internet by way of an Internet router and server, for the purpose of enabling different departments within a business organization (e.g. marketing, sales, engineering, support and service, advertising, finance, etc.) manage different types of UPN/URL links based on the type of information contained within the URL-specified information resource on the WWW;

FIG. 3A1 is a graphical representation of a first illustrative embodiment of the client computer system of the present invention, designed for use in desktop environments at home, work and play;

FIG. 3A2 is a graphical representation of a second illustrative embodiment of the client computer system of the present invention realized in the form of a bar code driven multi-media kiosk, designed for use as a “virtual or Cyber sales agent” in retail shopping environments, such as department stores, supermarkets, superstores, retail outlets and the like;

FIG. 3A3 is a graphical representation of a third illustrative embodiment of the client computer system of the present invention realized in the form of a bar code driven multi-media kiosk, designed for use as a “Cyber sales agent” in retail shopping environments such as department stores, supermarkets, superstores, retail outlets and the like, and shown as having an integrated “cord-connected” type laser scanning bar code symbol reader disposed overhead its LCD touch-screen panel, a telephone handset for carrying out telephone calls, and a credit card transaction terminal for conducting consumer purchase transactions and other forms of electronic commerce while using the consumer product information finding system of the present invention;

FIG. 3A3′ is a graphical representation of the bar code driven multi-media kiosk shown in FIG. 3A3, wherein the laser scanning projection-type bar code symbol reader is removed from its support stand, by pulling its connector cable out of its cable take-up unit, and used to read a bar code symbol on product located a relatively short distance away from the kiosk;

FIG. 3A4 is a graphical representation of a fourth illustrative embodiment of the client computer system of the present invention realized in the form of a bar code driven multi-media kiosk, designed for use as a “Cyber sales agent” in retail shopping environments such as department stores, supermarkets, superstores, retail outlets and the like, and shown as having an integrated “cordless” type laser scanning bar code symbol reader disposed overhead its LCD touch-screen panel, a telephone handset for carrying out telephone calls, and a credit card transaction terminal for conducting consumer purchase transactions and other forms of electronic commerce while using the consumer product information finding system of the present invention;

FIG. 3A4′ is a graphical representation of the bar code driven multi-media kiosk shown in FIG. 3A4, wherein the laser scanning projection-type bar code symbol reader is removed from its support stand and used to read a bar code symbol on a product located a relatively short distance away from the kiosk;

FIG. 3A5 is a graphical representation of a fifth illustrative embodiment of the client computer system of the present invention realized in the form of a consumer product information access terminal, designed for use as a “sales agent's tool” at a point-of-sale (POS) station in retail shopping environments, wherein the information access terminal has a bar code symbol reader integrated with the POS station for reading the UPC numbers on consumer products being offered for sale in the store, and also a LCD screen capable of being mounted in various viewing positions for displaying consumer product-related information accessed from a centralized database interconnected to the Internet;

FIG. 3A6 is a graphical representation of a sixth illustrative embodiment of the client computer system of the present invention realized in the form of a bar code driven multi-media kiosk, which is completely transportable within the store by the hand of a shopper for shopping convenience in retail environments such as department stores, supermarkets, superstores, retail outlets and the like;

FIG. 3A7 is a graphical representation of a seventh illustrative embodiment of the client computer system of the present invention realized in the form of a bar code driven multi-media kiosk, mounted upon a shopping cart or other vehicle for shopping convenience in retail environments such as department stores, supermarkets, superstores, retail outlets and the like;

FIG. 3A8 is a schematic representation of another embodiment of the transportable bar code driven product information access terminal of the present invention, realized using a Newton MessagePad 130 equipped with Nethopper http client software and a Motorola RF modem PCMCIA card, for wireless access to the Internet;

FIG. 3B is a schematic representation of an exemplary display screen produced by a (graphical user interface) Java GUI-based web browser program running on a client subsystem and providing an on-screen IPD Web-site Find Button (e.g. UPC REQUEST™ Central Website Find Button) for instantly connecting to the IPD Web-site (e.g. UPC REQUEST™ Central Website) and carrying out the consumer product information finding and serving method of the present invention;

FIG. 3C is a schematic representation of an exemplary display screen produced by a Java GUI-based Internet browser or communication program running on a client subsystem and displaying a Netscape-style browser “display framework”, served from the IPD Web-site (e.g. UPC REQUEST™ Central Website), and supporting or providing a sponsor frame for sponsor advertisement, a control frame with Check-Box type buttons for activating any mode of the IPI finding and serving subsystem, and an information frame for displaying HTML documents (instructions, forms, and the like) in accordance with the principles of the present invention;

FIG. 4A1 is a schematic representation of the relational-type IPI Registrant Database maintained by each IPD Server configured into the system of the illustrative embodiment of the present invention, showing the information fields for storing (i) the information elements representative of the UPN (e.g. UPC data structure, EAN data structure, and/or National Drug Code (NDC) data structure), URLs, trademark(s) (TM_(i)), Company Name (CNi) and company address, Product Description (PD_(i)), E-Mail Address (EMA_(i)) thereof symbolically-linked (i.e. related) for a number of exemplary IPI Registrants listed (i.e. registered) with the IPI Registrant Database maintained by each IPD Server, image files for registered consumer products, and consumer product information request (CPIR) enabling Applets for access by retailers, wholesalers, advertisers, Web publishers, and the like, and insertion within the HTML code of Web documents on various types of Internet information servers hosting WWW sites, as well as EC-enabled WWW-sites, EC-enabled stores and/or on-line e-commerce product catalogues, so that when executed, these CPIR-enabling Applets automatically access a categorized URL menu containing URLs (identified in FIG. 4A2) specifying the location of manufacturer-linked information resources on the Internet pertaining to a particular UPN-labeled product;

FIG. 4A2 is a schematic representation of the information subfield structure of the URL Information Field of the IPI Database of FIG. 4A1, showing the Product Advertisement Information Field, the Product Specification (Description/Operation) Information Field, the Product Update Information Field, the Product Distributor/Reseller/Dealer Information Field, the Product Warranty/Servicing Information Field, the Product Incentive Information Field thereof, the Product Review Information Field, the Related Products Information Field, and Miscellaneous Information Fields detailed hereinafter;

FIG. 4B is a schematic representation of the relational-type Non-IPI Registrant Database maintained by each IPD Server that is configured into the IPI Finding and Serving Subsystem of the illustrative embodiment of the present invention, showing the information fields for storing (i) the information elements representative of the Company Name (CNi) and Company Address, Trademark(s) (TM_(i)) registered by the associated Company, E-Mail Address (EMA_(i)) thereof symbolically-linked for a number of exemplary Non-IPI registrants listed within the Non-IPI Registrant Database maintained by each IPD Server, and CPIR enabling Applets for access by retailers, wholesalers, advertisers, Web publishers, and the like, and insertion within the HTML code of Web documents on various types of Internet information servers hosting WWW sites, as well as EC-enabled WWW-sites, EC-enabled stores and/or on-line e-commerce product catalogues, for the purpose described above;

FIG. 4C is a schematic representation of the structure of a relational database management subsystem (RDBMS) used to carry out a best-mode embodiment of the IPI Registrant Database represented in FIGS. 4A1 and 4A2 hereof;

FIG. 4C1 is a schematic representation illustrating the information fields of the table entitled “Manufacturer” used in the RDBMS shown in FIGS. 4A1 and 4A2 hereof;

FIG. 4C2 is a schematic representation illustrating the information fields of the table entitled “Consumer Product” used in the RDBMS shown in FIGS. 4A1 and 4A2 hereof;

FIG. 4C3 is a schematic representation illustrating the information fields of the table entitled “Information Resources on the WWW” used in the RDBMS shown in FIGS. 4A1 and 4A2 hereof;

FIG. 4D is a schematic representation illustrating the information fields of the table entitled “Retailer” used in the RDBMS shown in FIGS. 4A1 and 4A2 hereof;

FIGS. 4E1 and 4E2, taken together, provide a high-level flow chart describing the steps involved in the first illustrative method of creating, loading, distributing, embedding, displaying, and executing “server-side” consumer product information request (CPIR) enabling Applets when using the system architecture and servlet-based search and display mechanism schematically depicted in FIG. 2B1, enabling consumers to automatically search the RDBMS for consumer product information related to a particular UPN-specified product while visiting EC-enabled stores and other WWW sites without disturbing the point of presence of the consumer;

FIG. 4F1 is a schematic representation illustrating the method of FIGS. 4E1 and 4E2 being carried out using certain subcomponents of the system depicted in FIGS. 2-1, 2-2, and 2B1, in particular;

FIG. 4F2 is a schematic representation illustrating in greater detail the Applet-embedding step of the method of FIGS. 4E1 and 4E2, carried out using certain subcomponents of the system depicted in FIGS. 2-1 and 2-2;

FIGS. 4G1 and 4G2, taken together, provide a high-level flow chart describing the steps involved in the second illustrative method of creating, loading, distributing, embedding, displaying, and executing “client-side” consumer product information request (CPIR) enabling Applets when using the system architecture and Applet/CGI-based search and display mechanism schematically depicted in FIG. 2B2, enabling consumers to automatically search the RDBMS for consumer product information related to a particular UPN-specified product while visiting EC-enabled stores and other WWW sites without disturbing the point of presence of the consumer;

FIG. 4H1 is a schematic representation illustrating the method of FIGS. 4G1 and 4G2 being carried out using certain subcomponents of the system depicted in FIGS. 2-1, 2-2, and 2B2, in particular;

FIG. 4H2 is a schematic representation illustrating in greater detail the Applet-embedding step of the method of FIGS. 4G1 and 4G2, carried out using certain subcomponents of the system depicted in FIGS. 2-1 and 2-2;

FIGS. 4I1 and 4I2, taken together, provide a high-level flow chart describing the steps involved in the second illustrative method of creating, loading, distributing, embedding, displaying, and executing “client-side” consumer product information request (CPIR) enabling Applets when using the system architecture and Applet/socket-based search and display mechanism schematically depicted in FIG. 2B3, enabling consumers to automatically search the RDBMS for consumer product information related to a particular UPN-specified product while visiting EC-enabled stores and other WWW sites without disturbing the point of presence of the consumer;

FIG. 4J1 is a schematic representation illustrating the method of FIGS. 4I1 and 4I2 being carried out using certain subcomponents of the system depicted in FIGS. 2-1, 2-2, and 2B3, in particular;

FIG. 4J2 is a schematic representation illustrating in greater detail the Applet-embedding step of the method of FIGS. 4I1 and 4I2, carried out using certain subcomponents of the system depicted in FIGS. 2-1 and 2-2;

FIGS. 4K1 and 4K2, taken together, provide a high-level flow chart describing the steps involved in the fourth illustrative method of creating, loading, distributing, embedding, displaying, and executing “client-side” consumer product information request (CPIR) enabling Applets when using the system architecture and Applet/RMI-based search and display mechanism schematically depicted in FIG. 2B4, enabling consumers to automatically search the RDBMS for consumer product information related to a particular UPN-specified product while visiting EC-enabled stores and other WWW sites without disturbing the point of presence of the consumer;

FIG. 4L1 is a schematic representation illustrating the method of FIGS. 4K1 and 4K2 being carried out using certain subcomponents of the system depicted in FIGS. 2-1, 2-2, and 2B4, in particular;

FIG. 4L2 is a schematic representation illustrating in greater detail the Applet-embedding step of the method of FIGS. 4K1 and 4K2, carried out using certain subcomponents of the system depicted in FIGS. 2-1 and 2-2;

FIG. 4M1 is a graphical illustration of an Internet browser display screen that might be displayed on a client computer subsystem hereof while browsing the Library of CPIR-Enabling Java Applet (HMTL tags) maintained within the UPN/URL RDBMS shown in FIGS. 2-1 through 2A, wherein the user (e.g. retail purchasing agent, product catalog manager, advertising agent, or whomever) is provided with the option of viewing and downloading, for each UPN-specified product in the system, an executable file containing the HTML tag for either a client-side or server-side type CPIR-enabling Java Applet associated therewith;

FIG. 4M2 is a graphical illustration of an Internet browser display screen that might be displayed on a client computer subsystem hereof while browsing a product-specific page of an on-line business-to-business consumer product catalog, wherein the user (e.g. retail purchasing agent, product catalog manager, advertising agent, or whomever) is provided with the option of viewing and downloading, for each UPN-specified product offered for sale in the on-line catalog, an executable file containing the HTML tag for either a client-side or server-side type CPIR-enabling Java Applet associated with the UPN-specified consumer product;

FIGS. 4N1 and 4N2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while browsing a WWW information search engine or directory, such as Yahoo, Lycos, or Excite, looking for information on the WWW related to a particular consumer product, and launching a CPI search enabling GUI in accordance with the principles of the present invention by clicking on the (underlying) HMTL tag of either client-side or server-side Applet embedded within the HTML code of the displayed WWW page associated with the search engine/directory;

FIGS. 4O1 and 4O2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while shopping/browsing an EC-enabled storefront, looking for information on any consumer product which is carried within the retailer's EC-enabled store; and launching a CPI search enabling GUI in accordance with the principles of the present invention by clicking on the HMTL tag of a client-side or server-side Applet embedded within the HTML code of the displayed E-store Web page;

FIGS. 4P1 and 4P2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while shopping/browsing at a particular catalog page in an EC-enabled store, considering whether or not to make an on-line purchase of a particular consumer product displayed on the catalog page; and then initiating a UPN-directed CPI search according to the principles of the present invention by clicking on the HMTL tag of a UPN-encoded client-side or server-side Applet embedded within the HTML code of the displayed catalog page;

FIGS. 4Q1 and 4Q2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while visiting an on-line EC-enabled auction site (e.g. at http://www.ebay.com) when considering whether or not to place a bid on a particular consumer product displayed within the auction listings thereof, and then launching a CPI search enabling GUI in accordance with the principles of the present invention by clicking on the HMTL tag of a URL-encoded client-side or server-side Applet embedded within the HTML code of the displayed on-line auction Web page;

FIGS. 4R1 and 4R2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while shopping/browsing at a particular auction page in the EC-enabled auction site of FIGS. 4Q1 and 4Q2, considering whether or not to place at bid on a particular product up being auctioned; and then initiating a UPN-directed CPI search according to the principles of the present invention by clicking on the HMTL tag of a UPN-encoded client-side or server-side Applet embedded within the HTML code of the displayed auction page;

FIGS. 4S1 and 4S2 set forth graphical illustrations of Internet browser display screens that might be displayed on a client computer subsystem hereof while browsing a WWW page of any business, organization or ongoing concern, seeing an Internet product or service advertisement of particular interest on the WWW page, and then initiating a UPN-directed CPI search according to the principles of the present invention by clicking on the HMTL tag of a UPN-encoded client-side or server-side Applet embedded within the HTML code of the displayed WWW page;

FIG. 5A is a schematic diagram illustrating the high level structure of communication protocol that can be used among the client subsystem C_(a), the IPD Server S_(b), and the Web-based Document Server S_(WD)(30) of the IPI Finding And Serving Subsystem hereof when, from any particular client subsystem, the subsystem is engaged is in Manufacturer/Product Registration Mode of operation, requesting as input a URL which automatically connects the client subsystem to the Web Document Server associated with the Manufacturer/Product Registration Subsystem of the present invention;

FIG. 5B is a schematic diagram illustrating the high level structure of a communication protocol that can be used among the client subsystem C_(a), the IPD Server S_(b), and the IPI Server S_(c) of the IPI Finding and Serving Subsystem hereof when the subsystem is in its Manufacturer Website Search Mode of operation, requesting as input a UPN (e.g. UPC or EAN) associated with a manufacturer's product, and providing as output the URL of the home page of the manufacturer's Web-site and automatically displaying the same;

FIG. 5C is a schematic diagram illustrating the high level structure of a communication protocol that can be used among the client subsystem C_(a), the IPD Server S_(b), and the IPI Server S_(c) of the IPI Finding And Serving Subsystem hereof when the subsystem is in its UPN-Directed Information Access Mode of operation, requesting as input a UPN associated with the consumer product, and providing as output the set of URL(s) registered with the consumer product identified by the UPN within the database of the system and pointing to HTML-encoded documents containing particular types of product-related information;

FIG. 5D is a schematic diagram illustrating the high level structure of a communication protocol that can be used among the client subsystem C_(a), the IPD Server S_(b), and the IPI Server S_(c) of the IPI Finding And Serving Subsystem hereof when the subsystem is in its Trademark-Directed Search Mode of operation, requesting as input a trademark and/or company name, and providing as output the product descriptor(s) and a UPN (or set thereof) related to the trademark within the database of the system and pointing to HTML-encoded documents containing particular types of product-related information;

FIG. 5E is a schematic diagram illustrating the high level structure of a communication protocol that can be used among the client subsystem C_(a), the IPD Server S_(b), and the IPI Server S_(c) of the IPI Finding And Serving Subsystem hereof when the subsystem is in its Product-Description Directed Search Mode of operation, requesting as input a product descriptor related to the consumer product on which information is sought and providing as output the trademark, company name and URL(s) related to the product descriptor within the database of the system and pointing to HTML-encoded documents containing particular types of product-related information;

FIG. 6A provides a high level flow chart illustrating the steps involved in carrying out the communication protocol shown in FIG. 5A when the IPI Finding and Serving Subsystem is in its Manufacturer/Product Registration Mode of operation;

FIG. 6B provides a high level flow chart illustrating the steps involved in carrying out the communication protocol shown in FIG. 5B when the IPI Finding and Serving Subsystem is in its Manufacturer Website Search Mode of operation;

FIG. 6C provides a high level flow chart illustrating the steps involved in carrying out the communication protocol shown in FIG. 5D when the IPI Finding and Serving Subsystem is in its UPN-Directed Information Access Mode of operation;

FIGS. 6D1 through 6D3, taken together, provide a high level flow chart illustrating the steps involved in carrying out the communication protocol shown in FIG. 5C when the IPI Finding and Serving Subsystem is in its Trademark-Directed Search Mode of operation;

FIGS. 6E1 through 6E3, taken together, provide a high level flow chart illustrating the steps involved in carrying out the communication protocol shown in FIG. 5E when the IPI Finding and Serving Subsystem is in its Product-Description Directed Search Mode of operation;

FIG. 7 is a schematic representation of an exemplary embodiment of the IPI Finding and Delivery Subsystem of the present invention showing the various constituent subsystems thereof; and

FIG. 8 is a schematic representation of a portfolio of Web-sites supported and managed by the UPN/URL database management subsystem with the assistance of the manufacturer/product registration subsystem and Web-enabled client subsystems operated by manufacturers and/or their agents in accordance with the information management principles of the present invention.

BEST MODES FOR CARRYING OUT THE INVENTION

Referring to the accompanying Drawings, like structures and elements shown throughout the figures thereof shall be indicated with like reference numerals.

Overview of the System of the Present Invention

As illustrated in FIG. 1, the consumer-product information collection, transmission and delivery system of the present invention is generally indicated by reference numeral 1 and comprises an integration of information subsystems, namely: an IPI finding and serving subsystem 2 for allowing consumers to find product related information on the Internet (e.g. WWW) at particular Uniform Resource Locators (URLs), using UPC numbers and/or trademarks and tradenames symbolically-linked or related thereto; a UPC Product-Information Subsystem (“UPC Catalog”) 3 for providing retailers with accurate up-to-date product information on numerous consumer-products offered for wholesale to retailers by manufacturers registering their products therewith; a Electronic Trading Information Subsystem 4 for providing trading partners (e.g. a manufacturer and a retailer) to sell and purchase consumer goods by sending and receiving documents (e.g. purchase orders, invoices, advance slip notices, etc.) to consummate purchase and sale transactions using either Value Added Network (VAN) based EDI transmission or Internet (e.g. HTTP, SMTP, etc.) based electronic document communications; a Sales Analysis and Forecasting Information Subsystem 5 for providing retailers with information about what products consumers are currently buying at retail stores or expect to be buying in the near future; Collaborative Replenishment Information Subsystem 6 for determining what products retailers can be buying in order to satisfy consumer demand at any given point in time; a Transportation and Logistics Information Subsystem 7 for providing retailers with information about when ordered products (purchased by retailers at wholesale) will be delivered to the retailer's stores; and Input/Output Port Connecting Subsystems 8 for interconnecting the input and output ports of the above-identified subsystems through the infrastructure of the Internet and various value-added EDI networks of global extent. Notably, unlike prior art supply chain management systems, the consumer-product information collection, transmission and delivery system of the present invention embraces the manufacturers, retailers, and consumers of UPC-encoded products, and not simply the manufacturers and retailers thereof. As will become apparent hereinafter, this important feature of the present invention allows manufacturers and retailers to deliver valuable product related information to the consumers of their products, thereby increasing consumer purchases, consumer satisfaction and consumer loyalty. Prior art supply chain management systems have no way or means of providing such information services to the consumers of UPC-encoded products along the consumer-product supply and demand chain.

As shown in FIGS. 2-1 and 2-2, the consumer-product information collection, transmission and delivery system of FIG. 1 is realized as an arrangement of system components, namely: a central UPN/URL Database Management Subsystem 9 for storing and serving various types of consumer-product information to retailers, manufacturers and consumers alike (e.g., the name of the product's manufacturer; the Universal Product Code (UPC) or European Article Number (EAN) assigned to the product by the manufacturer; one or more URLs specifying the location of information resources on the Internet at which particular kinds of information relating to the consumer-product can be found; merchandise classification; style number; tradename; information specifying the size, color and other relevant characteristics of the consumer-product, where applicable; ordering criteria; availability and booking dates, etc.); a globally-based (packet-switched) digital telecommunications network (such as the Internet) 10 having an infrastructure including Internet Service Providers (ISPs), Network Service Providers (NSPs), routers, telecommunication lines, channels, etc., for supporting packet-switched type digital data telecommunications using the TCP/IP networking protocol well known in the art; one or more Internet Product Finding Directory (IPD) Servers, each indicated by reference numeral 11 and being connected to the Internet at strategically different locations via the Internet infrastructure 10 and data-synchronized with each other in order that each such Server maintains mirrored a relational-type database structure as represented in FIGS. 4A and 4B; a plurality of Internet Product-Information (IPI) Servers, each indicated by reference numeral 12 and being connected to the Internet via the Internet infrastructure; a plurality of retailer-related electronic-commerce (EC) information servers 12A, each operably connected to the infrastructure of the Internet, and enabling the hosting or one or more EC-enabled stores or EC-enabled on-line catalogues (i.e. EC-enabled WWW sites) owned, operated, managed and/or leased by one or more retailers along the retail supply and demand chain; a plurality of manufacturer-related electronic-commerce (EC) information servers 12B, each operably connected to the infrastructure of the Internet, and enabling the hosting or one or more EC-enabled stores or EC-enabled on-line catalogues (i.e. EC-enabled WWW sites) owned, operated, managed and/or leased by one or more manufacturers along the retail supply and demand chain; a plurality of User (or Client) Computers, each indicated by reference numeral 13, being connected to the Internet via the Internet infrastructure and available to consumers (C₁, C₂, C₃, . . . , C_(i)); one or more data communication (i.e. EDI) networks 14, comprising data collection nodes 15 and communication links 16, operably connected to the centralized UPN/URL Database Management Subsystem 9, each Client Computer 13 available to a Manufacturer (M₁, M₂, M₃, . . . , M_(j)) and Retailer (R₁, R₂, R₃, . . . , R_(k)) within the retail supply and demand chain; a Web-based Document Server 30 connected to at least one of the IPD Servers 11 and the Internet infrastructure, for transferring documents and messages to remote Client Computer Systems during the registration of manufacturers and consumer products with the system hereof and periodically updating product-related information with the IPD Servers 11 in an automatic manner; and a Web-based Document Administration Computer 31 connected to the Web-based Document Server 30 by way of a TCP/IP connection 32, for administrating the registration of manufacturers and products with the system, initiating the transfer of consumer product related information (e.g. menu of URLs) between the remote Client Computer Systems and Web-Based Document Server 30, transferring such information to the IPD Servers 11, and maintaining local records of such information transfers and the like. As will become apparent hereinafter, Web-based Document Server 30 and Web-based Document Administration Computer 31 provide a subsystem for (i) managing the process of registering qualified manufacturers and their consumer products and related Web pages (e.g. UPC numbers and URLs), and (ii) updating the product-related information with the IPD Servers 11 in an automatic manner to ensure accurate links between UPNs and URLs within the UPN/URL Database Management Subsystem. The subsystem comprising the Web-based Document Server 30 and Web-based Document Administration Computer 31 shall be referred to as the Manufacturer/Product Registration Subsystem of the consumer product information finding and delivery subsystem 2 and indicated by reference numeral 33 throughout the figure drawings hereof.

Preferably, the centralized UPN/URL Database Management Subsystem 9 and at least one of the IPD Servers 11 are located at a secured information storage/processing center 17, along with a multiprocessor (or mainframe) computer system, information servers, routers, data communication lines, disk storage devices (e.g. RAIDs), tape drives and tape-library system, uninterrupted power supplies (UPS), and other peripheral technology to provide on-line, batch and back-up operations. However, the IPI Servers, the Client Computers and the other IPD Servers (if provided for database mirroring purposes), typically will be located throughout the world, as the distribution of manufacturers, retailers and consumers who are encouraged to use the system is scattered across the Planet.

In the illustrative embodiment, the Web-based Document Server 30 is a Windows NT Server running WebDox™ Server software from Premenos Corporation of Concord, Calif. The Windows NT Server can be realized using a suitable computer system having a Pentium® or higher CPU, 64 MB of RAM or higher, running (i) Microsoft Windows NT Server 4.0 or higher Operating System software from Microsoft Corporation, (ii) Microsoft Internet Information Server 2.0 or higher from Microsoft Corporation, and (iii) Microsoft SQL Server 6.5 or higher software from Microsoft Corporation. Also, the WebDox™ Server is provided with a dedicated Internet connection (i.e. ISDN or better) to the Internet infrastructure 10.

The EDI administration computer 31 is either a Windows 95 or Windows NT Computer system running WebDox Admin™ software from Premenos Corporation of Concord, Calif. The Windows 95 or Windows NT computer system 31 can be realized using a suitable computer system having an Intel 486 or higher CPU, 12 MB of RAM or higher, running Microsoft Windows 95 or Windows NT 4.0 or higher, and having a TCP/IP connection 31 to the WebDoX™ Server 30.

In order to use the WebDox™ system, each remote Client Computer System 13 includes either a Windows 95 or Windows NT Computer system running WebDox Remote™ software from Premenos Corporation of Concord, Calif. The Windows 95 or Windows NT computer system 13 can be realized using a suitable computer system having an Intel 486 or higher CPU, 16 MB of RAM or higher, and a VGA monitor or better, and running (i) Microsoft Windows 95 or Windows NT 3.51 or higher Operating System (OS) software, and (ii) Microsoft Internet Explorer 3.0 or higher from Microsoft Corporation. Also, the WebDox Remote™ Server is provided with a dial-up Internet connection (i.e. 14,400 bps or better) to the Internet infrastructure. The function of the Web-based Document Server 30, Web-based Administration System 31 and remote client subsystems 13 running the Premenos® WebDox Remote™ software is to provide a Web-based Document Transport System for automatically transferring information (e.g. UPN/URLs) from manufacturers to the IPD Servers of the system in order to periodically update the same. While the illustrative embodiment of this Web-based Document Transport System has been described in terms of its implementation using the WebDox™ system from Premenos, it is understood that other commercially available electronic document transport systems (e.g. COMMERCE:FORMS™ Electronic Business Forms Package from Sterling Commerce, Inc., http://www.stercomm.com) can be used to carry out this subsystem. The operation of this Web-Based Document Transport System will be described in detail hereinafter with respect to the collection and delivery of consumer product-related information to the IPDs hereof.

The major subsystem components comprising the consumer-product information collection, transmission and delivery system of the present invention will be described in greater detail below.

In the illustrative embodiment of the present invention, the UPC Product-Information Subsystem 2 is realized using the UPN/URL Database Management Subsystem 9 and data communication networks 14 shown in FIGS. 2-1 and 2-2. Preferably, the product procurement services delivered by the UPN/URL Database Management Subsystem 9 are provided by modifying the prior art QRSolutions UPC Catalog currently implemented by QuickResponse Services, Inc., so that this subsystem includes the database structures (i.e. information fields and data elements) of the IPD Database Server 11 which are neither found in nor suggested by the prior art QRSolutions UPC Catalog. The structure and operation of the UPN/URL Database Management Subsystem and IPD Server of the present invention will be described in greater detail hereinafter. The information services supported by the UPC Product-Information Subsystem 3 include those provided by the prior art QRSolutions UPC Catalog, and also a number of additional information services that can be used to carry out Product Registration within the IPI Finding and Serving Subsystem of the present invention. These additional information services will be described in greater detail hereinafter with reference to FIG. 2A.

The Electronic Trading Information Subsystem 4 is realized using the UPN/URL Database Management Subsystem 9, Client Computer Systems 13 and data communication networks 14 of the technology platform shown in FIGS. 2-1 and 2-2. Preferably, the inventory procurement services delivered by the Electronic Trading Subsystem 4 are provided by the prior art QRSolutions Econnect and Electronic Data Interchange Services currently being implemented by QuickResponse Services, Inc.

Sale Analysis and Forecasting Information Subsystem 5 is realized using information storage/processing center 1, Client Computer Systems 13, and the data communication networks 14 of the enabling technology platform shown in FIGS. 2-1 and 2-2. Preferably, the product inventory management services delivered by the Sale Analysis and Forecasting Information Subsystem 5 are provided by the prior art QRSolutions Sale Analysis and Forecasting Information Services currently being implemented by QuickResponse Services, Inc.

The Collaborative Replenishment Information Subsystem 4 is realized using information storage/processing center 17, Client Computer Systems 13 and the data communication networks 114 of the enabling technology platform shown in FIGS. 2-1 and 2-2. Preferably, the product inventory management services delivered by the Collaborative Replenishment Information Subsystem 6 are provided by the prior art QRSolutions Replenishment Services currently being implemented by QuickResponse Services, Inc.

The Transportation and Logistics Information Subsystem 7 is realized using information storage/processing center 17, Client Computer Systems 13, and the data communication networks 14 of the enabling technology platform shown in FIGS. 2-1 and 2-2. Preferably, the product distribution management services delivered by the Transportation and Logistics Information Subsystem 7 are provided by the prior art QRSolutions EDI and Logistics Management Services currently being implemented by QuickResponse Services, Inc.

In the illustrative embodiment of the system of the present invention, each Client Computer Subsystem 13 has a conventional Java GUI-based web browser program (e.g. Netscape, Internet Explorer, Mosaic, etc.) with a plug-in type module, such as CyberFinder™ navigational software by Aladdin Systems, Inc., of Watsonville, Calif., that provides an on-screen graphical icon for a “IPI Web-site Find” function. An exemplary display screen 18 produced by such a Java GUI-based web browser program is set forth in FIG. 3B. Alternatively, the URL of the home page of the IPI Web-site can be recorded as a browser “bookmark” for easy recall and access through a conventional Java GUI-based Internet browser. Once at the home page of the IPI Web-site, an Internet user can find product-related information on the Internet in essentially the same way as when using the web browser program of FIG. 3B. As shown, the on-screen radio button 19 functions as an “IPI Web-site Find” Button (or Consumer Product Information Button) for instantly connecting the client subsystem to a particular IPI Web-site (i.e. hosted on each mirrored IPD Server) and especially adapted for carrying out the IPI finding and serving method of the present invention. As will be described in greater detail hereinafter, examples of “IPI Web-sites” can include, but are not limited to: (1) one or more mirrored UPC Request Central Web-sites from which consumer product information from all manufacturers is available for access to consumers from predetermined Internet domains; and (2) an UPC Request Retail Web-site, for each retailer, wherein consumer product information associated with only manufacturers of products offered by the retailer is available for access to consumers from predetermined Internet domains within physical retail “brick and mortar” stores and “electronic commerce enabled stores.

In general, each IPI Web-site can be sponsored by a retail store subscribing to the consumer product information service hereof, or by one or manufacturers and/or service providers. The URL for the home page of any particular IPI Web-site can be selected with marketing considerations in mind, for example, “http://www.ipf.com” or “http://www.upcrequest.com” similar in form with the URLs of other information search-engines and directories currently available on the Internet. Upon selecting the IPI Web-site Find Button 19 (e.g. by a clicking of the mouse thereon shown in FIGS. 3B and 3C), the user is automatically connected to the home-page of the IPI Web-site (hosted on each mirrored IPD Server) which, as shown in FIGS. 3B and 3C, supports a Netscape-style “framework”, within which web pages accessed through the IPI web-site are displayed. An excellent tutorial on “framing” entitled “The Netscape Frames Tutorial™ (2nd edition)” by Charlton D. Rose set forth at the URL: “http://www.newbie.net/frames/”, last visited by Applicant on Mar. 26, 1997.

In general, the HTML-encoded documents served from the IPD Servers 11 hereof to the client subsystems 13 hereof will preferably have a three-field Netscape-style display framework which provides a unique and effective way of satisfactorily addressing the needs of consumers, hosting retailers, manufacturers and the IPI provider(s)/publishers alike. In practice, the Netscape-style browser “framework” can simultaneously accommodate the needs of the consumers using the particular Client Subsystems of the present invention, as well as the needs of the retailers who typically will host client subsystems hereof either (1) physically within their stores, and/or (2) electronically on their WWW sites using Web browser framing techniques as well.

As shown in FIG. 3C, the first (top-most) display field, the sponsor frame 20A, can be used to display to the consumer, a Web page (e.g. HTML-encoded document) containing a message that the IPI Finding and Serving Subsystem is being delivered to the consumer by the IPI Provider under, for example, the sponsorship of either: (1) the hosting retailer; (2) one or more advertisers posting advertising “banners” in the display frame 20A; or (3) the consumer himself/herself by paying a subscription fee or the like. Understandably, the method of sponsorship employed will vary from embodiment to embodiment of the present invention. An exemplary message for this display screen might read, for example, as follows:

-   “Welcome to the UPC Request™ Consumer Product-Information Finding     and Serving System sponsored by THE HOME DEPOT for your shopping     convenience and pleasure.”     The height of the sponsor frame 20A need only be a small fraction of     the consumer's display screen (e.g. ¾ inches) to convey this message     to the consumers during use of the IPI Finding and Serving Subsystem     of the present invention within the retailer's real (or     virtual/electronic) shopping environment.

As shown in FIG. 3C, the second (left-most) display field, the control frame 20B, is used to display an HTML-encoded document containing a Java GUI-based “control panel” 21 for the consumer product information finding and serving subsystem of the present invention. In the illustrative embodiment, this control panel 21 includes six Check Box type buttons, namely: a first Check Box type button 21A which, when selected, automatically activates the Manufacturer/Product Registration Mode of the subsystem; a second Check Box type button 21B which, when selected, automatically activates the Manufacturer Website Search Mode of the subsystem; a third Check Box type button 21C which, when selected, automatically activates the UPN-Directed Information Access Mode of the subsystem; a fourth Check Box type button 21D which, when selected, automatically activates the Trademark-Directed Search Mode; a fifth Check Box type button 21E which, when selected, automatically activates the Product-Description Directed Search Mode of operation of the subsystem; and a sixth Check Box type button 21F which, when selected, automatically activates the UPC-Encoded-Applet-Download/Distribution Mode of operation of the subsystem. Each of these Check Box type buttons is hot-linked to a particular HTML-encoded document residing on the IPD Server(s) 11 of the subsystem hereof.

While the IPI Web-site of the illustrative embodiment has a framework characterized by three-display fields, namely, the sponsor frame 20A, the control frame 20B, and the information display frame 20C, it is understood, however, that there may be more or fewer display frames than that shown in FIG. 3C. Each frame will act as a separate display screen where variables such as web-pages, scrolling, page colors, etc., are independently controllable.

As will become apparent hereinafter, one of the primary functions of the client subsystems 13 hereof is to provide UPN-driven consumer product information (CPI) GUIs within both “physical “brick and mortar” retail stores” and “E-commerce” enabled retail stores and product catalogues. Hereinafter, UPN-driven CPI GUIs provided within physical retail shopping environments will be referred to as “physical” or “physically-based” UPN-driven CPI kiosks, whereas UPN-driven CPI GUIs provided within E-commerce enabled retail shopping environments will be referred to as “cyber” UPN-driven CPI kiosks, despite the fact that these devices may provide the substantially the same type of consumer product information services to consumers, retailers and manufacturers along the retail supply and demand chain.

Physically-based UPN-driven CPI consumer product information kiosks will have great utility in physical retail shopping environments. However, such subsystems will be of little value to consumers browsing the Internet and shopping at EC-enabled WWW sites, unless they are located in “brick and mortar” type retail stores wherein consumers are provided with the option of shopping and conducting e-commerce transactions therein for all or selected items of merchandise offered for sale by the retailer. Moreover, when shopping in any particular retailer's EC-oriented store, however realized, it is also understood that great efforts must be undertaken to ensure that the shopper does not leave the EC-oriented store prior to making a purchase at the checkout page of the EC-oriented WWW site. Requiring, prompting or otherwise encouraging a shopper to link over to the IPD WWW site hereof (e.g. hosted on the IPD information server) for desired consumer product related information oftentimes presents a great risk that the shopper will not return to the EC-oriented store, at which he or she was once visiting, but rather will visit another EC-oriented store to make the product purchase.

The above limitations of physically-based consumer product information kiosks and the risks associated with consumer behavior while shopping on the Internet are overcome by the UPN-based cyber kiosks of the present invention. The primary function of UPN-based cyber CPI kiosks is to provide consumers with a simple and effective way of and means for producing UPN-driven CPI graphical user interfaces (GUIs) at the consumer's point of presence (POP) which may exist, for example, when: (i) shopping at EC-enabled stores, product catalogs and other types of EC-oriented WWW sites; (ii) reviewing and responding to Internet-based product advertisements (including Web-based discount coupons and the like) published at selected sections of Web-documents served from diverse types of WWW sites hosted on the millions of Internet information servers connected to the infrastructure of the Internet; and/or (iii) encountering a Web-document addressing a particular consumer product under review, analysis or other form of observation where accurate consumer product related information is desired or required by the consumer, whomever they might be. The details of producing UPN-enabled CPI GUIs in both physical and cyber retail environments will be described hereinafter.

As shown in FIG. 1, each synchronized IPD Server 11 is interfaced with an ISP 10A in a conventional manner. The actual number of IPD Servers 11 used in any particular application will depend on various factors including, for example, user demand, Internet traffic conditions, network router capacity and performance, etc. Each such IPD Server 11 is assigned a static IP address and a common domain name on the Internet according to the Domain Name System (DNS) well known in the art. Data synchronization among such databases can be achieved using conventional data synchronization techniques well known in the art. In addition, a backup and mirroring program can be used to maintain data security. Preferably, the synchronized IPD Servers are maintained by a team of network managers under the supervision of one or more webmasters.

As shown in FIGS. 2B1 through 2B4, using presently known technology available for use on the WWW, there are at least four different ways of configuring IPD Server 11 and back-end UPN/URL Database Management Subsystem 9 of the illustrative embodiment. These four different subsystem architectures are schematically depicted in FIGS. 2B1 through 2B4.

In the system architectures shown in FIGS. 2B2 through 2B4, client-side Applets (“Applets”), having their <APPLET> HMTL tags embedded within HTML documents (e.g. using the HTML 3.2 Specification), are executed with Java-enabled browsers on the client-side of the information network. In the system architecture set forth in FIG. 2B1, server-side Applets (“Servlets”), having their <SERVLET> HMTL tags embedded within HTML documents (e.g. the HTML 3.2 Specification), are executed within Java-enabled Web servers on the server-side of the information network. Collectively, client-side Applets and server-side Applets shall be referred to as “Applets”, wherein the major distinction between these two types is based on where the Applet is executed on the network (i.e. client-side or server side).

In each of these four system architectures, the IPD Server 11 performs a number of basic functions, for example: (1) serving HTML-encoded documents associated with IPD Web-sites (e.g. UPC Request Central WWW site, UPC Request Retail WWW sites, etc.) to client subsystems 13 on the Internet so as to enable the six primary modes of operation of the consumer product information finding and delivery subsystem hereof including, but not limited to, access to consumer product related information stored within the IPI and Non-IPI Registrant Databases on the UPN/IURL Database Management Subsystem 9; as well as (2) serving Libraries of executable files containing “UPN-enabled Java Applet tags” for client-side Applets as well as server-side Applets a/k/a “Servlets”, so as to enable retailers, manufacturers, advertisers, et al to download the executable “Applet tag containing” file to client subsystems.

According the first system architecture shown in FIG. 2B1, the UPN/URL Database management Subsystem 9 is realized by a SQL-based RDBMS server 9, whereas the IPD server 11 is realized by a Java Web Server 11′, provided with Java servlet support, and operably connected to the RDBMS server 9 by way of high-speed digital transmission link known in the art. During system operation, the Java Web Server 11′ serves to a Java-enabled client subsystem 13, an HTML-encoded document containing a servlet HMTL tag <SERVLET> which, upon selection by a single mouse-clicking operation by the consumer, sends an http request to the Java Web Server 11′, invoking a prespecified UPN-encoded servlet stored therewithin, causing the CPIR-enabling servlet to execute on the server-side of the network. This causes the servlet to call and run certain predefined Java methods which carry out a UPN-specified CPI search on the RDBMS server 9 and return the search results to the client subsystem 13 for display within a predetermined GUI generated therewithin. Using this system architecture, each UPN-encoded servlet executed within the Java Web Server 11′ will contain information relating to (1) the UPN-specified consumer product on which product information is to be searched for within the RDBMS server 9, (2) licensing information relating to whom the CPIR-enabling servlet has been licensed (although this architecture does not enable easy enforcement of the granted license as the servlet is executed on the server side of the network.

According to the second system architecture shown in FIG. 2B2, the UPN/URL Database management subsystem 9 is realized by a SQL-based RDBMS server 9, whereas the IPD server 11 is realized by a Java Web Server 11″, providing Java Applet support and being operably connected to the RDBMS Server 9 by a high-speed digital data transmission link known in the art. During system operation, the Java Web Server 11″ serves to the Java-enabled client subsystem 13, an HTML-encoded document containing a “UPN-encoded” Applet HMTL tag <APPLET> which, upon selection by a single mouse-clicking operation by the consumer, causes the CPIR-enabling Applet to execute on the client-side of the network, sending an http request to the Java Web Server 11″, invoking a prespecified Common Gateway Interface (CGI) stored within the Java Web Server 11″. This causes the Applet to call and CGI to run certain predefined methods for carrying out a UPN-specified CPI search on the RDBMS server 9 and returning the search results to the client subsystem 13 for display within a predetermined GUI prespecified within the Applet. Using this system architecture, each UPN-encoded Applet executed within the Java browser of the client machine 13 will contain information relating to (1) the UPN-specified consumer product on which product information is to be searched for within the RDBMS serverm9, (2) licensing information relating to whom the client-side Applet has been licensed and by whom the Applet may be served within the terms of the licensing program, etc.

According to the third system architecture shown in FIG. 2B3, the UPN/URL Database Management Subsystem 9 is realized by a SQL-based RDBMS server 9, whereas the IPD server 11 is realized by a Java Web Server 11′″, providing client-side Applet support, and being operably connected to the RDBMS server 9 by way of a high-speed digital data transmission link known in the art. During system operation, the Java Web Server 11′″ serves to the Java-enabled client subsystem 13, an HTML-encoded document containing a UPN-encoded Applet HMTL tag <APPLET> which, upon selection by a single-mouse clicking operation by the consumer, causes the Applet to execute on the client-side of the network, creating a “socket-type” connection at lower (TCP/IP) communication layers between the client subsystem 13 and Java Web Server 11′″, enabling the Java Web Server 11′″ to run certain predefined Java methods for carrying out a UPN-specified CPI search on the RDBMS server 9, and returning the search results to the client subsystem 13 for display within a GUI prespecified within the Applet. Using this system architecture, each UPN-encoded Applet executed within the Java client subsystem 13 will be created to contain information relating to (i) the UPN-specified consumer product on which product information is to be searched for within the RDBMS server 9, (ii) licensing information relating to whom the client-side Applet has been licensed and by whom the Applet may be served within the terms of the licensing program, etc.

According to the fourth system architecture shown in FIG. 2B4, the UPN/URL Database Management Subsystem 9 is realized by a SQL-based RDBMS server 9, whereas the IPD Server 11 is realized by a Java Web Server 11″″, supporting client-side Applet execution and being operably connected to a high-speed digital data communication link well known in the art. During system operation the Java Web Server 11″″ serves to the Java-enabled client subsystem 13, an HTML-encoded document containing a Applet HMTL tag <APPLET> which, upon selection by a single mouse-clicking operation by the consumer, causes the CPIR-enabling Applet to execute within the Java-enabled client 13 on the client-side of the network, calling a Remote Invocation Method to carry out a prespecified CPI search on the RDBMS server 9 and returning the search results to the client subsystem 13 for display within a predetermined GUI prespecified by the Applet. Using this system architecture, each UPN-encoded Applet executing within the Java enabled client 13 will contain information relating to (1) the UPN-specified consumer product on which product information is to be searched for within the RDBMS server, (2) licensing information relating to whom the server-side Applet has been licensed and by whom the Applet may be served within the terms of the licensing program, etc.

In the first illustrative embodiment shown in FIG. 2B1, Java (enabled) Web Server 11′ can be realized by, for example, the Origin 200 Server or the O₂ Desktop Workstation from Silicon Graphics, Inc, a high-end SUN information server from Sun Microsystems, Inc., or any other suitable computing machine, running: (1) JDBC Interface software for providing a uniform access to a wide range of relational databases on RDBMS server 9 (if necessary in a particular application of the system hereof) and providing a common base on which higher level tools and interfaces can be built; and (2) a servlet-enabled Web (http) server software program such as, the Java Web Server (JWS) 1.0 or later from JavaSoft, division of Sun Microsystems, Inc., or the JigSaw Web Server from the World Wide Web Consortium, each proving native Java support, or alternatively, the Fastrak™ Web (http) server from Netscape Communications, Inc., the Internet Information Server (IIS) from the MicroSoft Corporation, the Apache HTTP Server from The Apache Software Foundation at http://www.apache.org, or any other http server capable of transporting HTML-encoded documents, in conjunction with the Java Servlet Developer's Kit from JavaSoft, or the Servlet Express Tool from IBM Research Labs in Haifa, Israel, for managing servlets on Web servers lacking native Java support. In order to develop servlets, the Java Web Server 11′ should also be equipped with the following software tools: the Sun Java Developers Kit 1.1..x from Sun Microsystems, Inc.; and the Java Servlets Development Kit (JDSK) from Sun Microsystems, Inc., or a Java Development Environment that supports JDK 1.1.x, such as VisualAge for Java by IBM, MicroSoft's Visual J++, or the like. Optionally, the Java Web Server 11′ may also include Web-site development software (e.g. based on the HTML 3.2 or 4.0 Specification) for creating and maintaining the IPI Web-sites of the present invention, although such tools will be typically run on client subsystem 13 for practical reasons.

In the illustrative embodiments of FIGS. 2B2 through 2B4, Java Web Servers 11″ through 11″″ can be realized by, for example, the Origin 200 Server or the O₂ Desktop Workstation from Silicon Graphics, Inc, a high-end SUN information server from Sun Microsystems, Inc., or any other suitable computing machine, running: (1) JDBC Interface software for providing a uniform access to a wide range of relational databases on RDBMS server 9 (if necessary in a particular application of the system hereof) and providing a common base on which higher level tools and interfaces can be built; (2) a Web (http) server such as the Java Web Server (JWS) from JavaSoft, the JigSaw Web Server from the World Wide Web Consortium, the Internet Information Server (IIS) from the MicroSoft Corporation, the Apache HTTP Server from the Apache Software Foundation, or other Java-enabled Web server capable of transporting HTML encoded documents; (3) the Sun Java Developers Kit, from Sun Microsystems, Inc., for developing client-side Applets; and (4) optionally, Web-site development software (e.g. based on the HTML 3.2 or 4.0 Specification) for creating and maintaining the IPI Web-sites hereof, although such tools will typically run on client subsystems 13 for practical reasons. Notably, when using the Microsoft IIS, one can use a Java Development Environment that supports JDK 1.1.x, such as VisualAge for Java by IBM, MicroSoft's Visual J++, and the like. Also, Java Web Server 11″ must provide support for running CGI scripts written in Java, PERL or other suitable scripting language known in the art.

In the illustrative embodiments shown in FIGS. 2B1 through 2B4, each SQL-based RDBMS Server 9 can be realized by, for example, the Origin 200 Server from Silicon Graphics, Inc., the O₂ Desktop Workstation from Silicon Graphics, Inc., a ULTRA™ information server from Sun Microsystems, Inc., or any other suitable computing machine, running a RDBMS software program such as ORACLE 8.0 from Oracle Corporation, Sybase SQL from Sybase, Inc., Access 98 from Microsoft, or other database development program based on a database programming language such as the SQL Language, the Sybase language, or any other suitable database language enabling database programming and connectivity over the Internet.

In principle, there can be millions of IPI Servers 12 within the system hereof, each enabled to serve Web-based documents containing consumer product related information. Notably, each such IPI Server 12 can be realized by, for example, the Origin 200 Server from Silicon Graphics, Inc, the O2 Desktop Workstation from Silicon Graphics, Inc., the ULTRA™ information server from Sun Microsystems, Inc., or any other computing machine (e.g. desktop, palmtop, laptop, etc.) running an operating system (e.g. UNIX, LINUX, Macintosh, MS Windows, etc.) capable of performing the functions of an Internet (http) information server in a client-server distributed object computing environment. As shown in FIGS. 2-1 and 2-2, each IPI Server 12 is interfaced with an ISP 10A in a conventional manner. Each such IPI Server 12 is assigned a static IP address and a unique domain name on the Internet. Each IPI Server 12 is also provided with (i) Web-site development software for creating HTML-encoded multi-media pages for Web-site development, and (ii) Web-site server software for supporting HTTP and serving HTML, XML and other document formats used to construct hypermedia-type Web-sites containing product related information of a multi-media nature. Such Web-sites can be expressed in HTML, XML, SGML and/or VRML or any other suitable language which allows for Web-site construction and Web-site connectivity. Web-site management software can be used to maintain correct hyper-links for any particular Web-site. Preferably, the IPI Servers 12 are maintained by a team of network managers under supervision of one or more webmasters.

Each retailer-related electronic-commerce (EC) information server 12A indicated in FIGS. 2-1 and 2-2 is operably connected to the infrastructure of the Internet. In general, each retailer-related information server 12A can be realized by, for example, the Origin 200 Server or O2 Desktop Workstation from Silicon Graphics, Inc., a high-end information server from Sun Microsystems, Inc., or any other computing machine that can perform the function of a Server in a web-based, client-server type computer system architecture of the illustrative embodiment. As shown in FIGS. 2-1 and 2-2, each retailer-related EC-enabled information server 12A is interfaced with an ISP 10A in a conventional manner, and is assigned a static IP address and a unique domain name on the Internet. Each retailer-related EC-enabled information server 12A is also provided with: (i) Java-enabled WWW (http) server software, such as Netscape Communications FastTrak Information Server software, for supporting http, ftp, XML/ICE and other Internet protocols, and serving HTML and XML formatted documents (i.e. pages) associated with Web-sites containing product related information of a multi-media nature; (ii) an advanced EC-enabled product merchandising software solution, such as the Host and Merchant (or Enfinity) Intershop 4 E-Commerce Server Solution from Intershop Communications, Inc., of San Francisco, Calif., and/or catalogMANAGER® and catalogMAKER® software programs from RealEDI, Inc. of Sherman Oaks, Calif., for building, managing and operating all aspects of e-commerce WWW sites, whether implementing on-line merchandising solutions for retailers and manufacturers, creating business-to-business and business-to-consumer product catalogs; (iii) an Internet Advertisement Management Software Solution, such as OPEN ADSTREAM™ Internet AD management software solution by REAL-MEDIA, Inc. of New York, N.Y.), for managing all aspects of Internet advertising on Internet information servers; and optionally (iv) Web-site development software for enabling the creation of HTML-encoded multi-media pages and the like for the EC-enabled Web-site development. Such EC-enabled Web-sites can be expressed in HTML, XML and/or VRML or any other suitable language which allows for Web-site construction and Web-site connectivity. Web-site management software can be used to maintain correct hyper-links for any particular Web-site. Preferably, each EC-enabled retailer-related server 12A is maintained by a team of network managers under supervision of one or more webmasters. The primary function of each retailer-related EC information server 12A is to enable the hosting of one or more EC-enabled stores or EC-enabled on-line catalogues (i.e. WWW sites) owned, operated, managed and/or leased by one or more retailers, (and optionally wholesalers and manufacturers as well) along the retail supply and demand chain. The use of the Intershop 4 Hosting and Merchant E-commerce software solution enables sellers to design and build dynamic environments for buyers and sellers by enabling sellers (i.e. vendors) to: (1) create a unique look and feel for their e-commerce sites using a Web browser; (2) fully customize their e-commerce sites to maximize the buyers experience, using an import/export function for easily importing existing product databases and site design directly into the Intershop; (3) build detailed profiles of buyers and present them with products that match these profiles, creating a personalized shopping experience; and (4) offer complementary products for sale based on current selections, thereby raising the overall value of each e-commerce transaction carried out. Also, the back-office portion of the Intershop 4 E-commerce Solution is intuitively organized to make it easy for sellers to manage their on-line business through a Web browser.

Each manufacturer-related electronic-commerce (EC) information server 12B indicated in FIGS. 2-1 and 2-2 is operably connected to the infrastructure of the Internet. In general, each manufacturer-related EC information server 12B can be realized by, for example, the Origin 200 Server from Silicon Graphics, Inc., the O2 Desktop Workstation from Silicon Graphics, Inc., the ULTRA™ information server from Sun Microsystems, Inc., or any other computing machine that can perform the function of a http server in a client-server distributed object computing environment. As shown in FIGS. 2-1 and 2-2, each manufacturer-related EC-enabled information server 12B is interfaced with an ISP 10A in a conventional manner, and is assigned a static IP address and a unique domain name on the Internet. Each manufacturer-related EC-enabled information server 12B is also provided with: (i) Java-enabled WWW (http) server software, such as Netscape Communications FastTrak Information Server software, for supporting http, ftp, and other Internet protocols, and serving HTML and XML formatted documents (i.e. pages) associated with Web-sites containing product related information of a multi-media nature; (ii) an advanced EC-enabled product merchandising software solution, such as the Host and Merchant Intershop 4 E-Commerce Server Solution from Intershop Communications, Inc., of San Francisco, Calif., and/or catalogMANAGER® and catalogMAKER® software programs from RealEDI, Inc. of Sherman Oaks, Calif., for building, managing and operating all aspects of e-commerce WWW sites, whether implementing on-line merchandising solutions for retailers and manufacturers, or creating business-to-business and business-to-consumer product catalogs; (iii) an Internet Advertisement Management Software Solution, such as OPEN ADSTREAM™ Internet AD management software solution by REAL-MEDIA, Inc. of New York, N.Y.), for managing all aspects of Internet advertising on Internet information servers; and optionally (iv) Web-site development software for enabling the creation of HTML-encoded multi-media pages and the like for the EC-enabled Web-site development. Such EC-enabled Web-sites can be expressed in HTML, XML, SGML and/or VRML or any other suitable language which allows for Web-site construction and Web-site connectivity. Web-site management software can be used to maintain correct hyper-links for any particular Web-site. Preferably, each EC-enabled manufacturer-related server 12B is maintained by a team of network managers under supervision of one or more webmasters. The primary function of each manufacturer-related EC information server 12B is to enable the hosting or one or more EC-enabled stores or EC-enabled on-line catalogues (i.e. WWW sites) owned, operated, managed and/or leased by one or more manufacturers, (and optionally wholesalers and retailers as well) along the retail supply and demand chain.

Each Client Computer Subsystem (hereinafter “client subsystem”) 13 can be realized by any computing system employing operating system (OS) software (e.g. Macintosh, Windows 95, Windows NT, Unix, etc.) which supports a Java-enabled Internet browser program (e.g. Netscape's Navigator, MicroSoft's Explorer, NCSC's Mosaic, etc.). The operating system should also include: (1) Internet networking software that supports the TCP/IP networking protocol (required by HTTP, FTP and the like) and provides a JAVA GUI-based Web browser interface; and, in the case of client computer machines 13 that are used by manufacturers and retailers in their “back office” operations, (2) Electronic Data Interchange (EDI) networking software that supports all versions of EDI between two or more client subsystems over the VAN-based or Web-based EDI networks illustrated in FIGS. 2-1 and 2-2. Alternatively, client subsystems may also be realized by any of the following systems: (i) a Newton MessagePad 130 (running the Newton 2.0 Operating System and NetHopper™ Internet Software and equipped with a Motorola RF PCMCIA modem card); (ii) a Pippin™ computer system from Apple Computer, Inc.; (iii) a PalmPilot VII wireless Internet-enabled palmtop computing device by 3COM, Inc.; (iv) a network computer (NC) that supports the Java™ programming language and Java applets expressed therewith; (v) a Sony® WebTV Internet Terminal (supported by the WebTV Service provided by WebTV Network, Inc.); or the like. As shown in FIG. 1, each Client Computer is interfaced with an ISP 10A in a conventional manner. Each such client subsystem may be assigned a static IP address and a unique domain name on the Internet, or one may be dynamically assigned thereto by way of its ISP depending on its connectivity, and set of assigned functions within the consumer product information network of the present invention. Optionally, any client subsystem may include Web-site (http) server software serving Web documents of various formats (HTML, XML, SGML or the like) from one or more hypermedia-type Web-sites in a manner well known in the art.

Typically, each client subsystem 13 will be maintained by either present or future manufacturers, retailers and/or consumers of products, about which information can be found on the Internet. As shown in FIG. 3A1, any client subsystem of the present invention may be realized as a desktop computer workstation comprising: a processor and memory 19; a visual display monitor 20; a keyboard 21; a JAVA GUI mouse 22; and a bar code symbol reader 23 for reading UPC, UPC/EAN and other types of bar code symbols printed on consumer products, brochures, documents, and the like.

As shown in FIG. 3A2, any Client Computer 13 may also be realized in the form of a Web-based (wired or wireless) multi-media kiosk, designed for use as a “Cyber sales agent” within retail shopping environments. As shown in FIG. 3A2, the Web-based kiosk of the present invention- may comprise: a floor, wall or ceiling supported housing 25; an omnidirectional laser bar code symbol reader (e.g. Metrologic MS 6720 Laser Scanner) 26 for reading UPC (and other types of) symbols printed on products, brochures, documents and the like; an active-matrix LCD-type visual display screen 27 for viewing product related information automatically displayed thereon in response to the entry of the UPC numbers scanned into the UPC Number Entry Window 21D below the IPI Finder button 21A of Control Strip 20B displayed on the client subsystem, as shown in FIG. 3C; a touch-screen type keyboard and pointing device 28 for clicking on anchored links on Web pages, entering information into client subsystem during its use; audio-speakers 29A for supporting multimedia Web-sites that may be visited when using the client subsystem; a color or black/white printer for printer 29B for printing out Web pages under consumer command during an information finding session using the system; and also, one or more floppy-disc (or otherwise removable) drive units 29C, accessible to the consumer for recording promotional and trial versions of information-based consumer products (e.g. video and audio recordings, computer software products, and the like) on removable information storage media (e.g. 1.44 MB floppy discs, 100 MB Zip® floppy discs, 1 GB Jazz® floppy discs, etc.) supplied by either the retailer or consumer. Optionally, the kiosk can be provided with a stereoscopic micropolarizing LCD panel from Vrex, Inc. of Elmsford, N.Y. so that micropolarized spatially-multiplexed images (SMIs) of 3-D objects represented with VRML-encoded Web pages can be stereoscopically perceived by consumers when viewed through either an electrically-passive polarizing visor structure supported from the housing of the kiosk, or a pair of polarizing eyeglasses tethered to the kiosk housing and donned by the consumer. Notably, by virtue of its compact size and low power requirements, this Web-based kiosk can be easily located in supermarkets, department stores, superstores, home-centers, discount retail outlets, or any other public location where consumer-products are being sold, offered for sale, and/or serviced.

As shown in FIG. 3A3, any Client Computer 13 within the system hereof may be realized in the form of the Web-based multi-media kiosk 34, also designed for use as a “virtual sales agent” within retail shopping environments. As shown, the Web-based kiosk 34 comprises: an ultra-compact housing 35 capable of being supported upon a pair of support rods (35A), a vertical support surface (e.g. wall), a horizontal support surface (e.g. countertop), or supported from a ceiling or pedestal; an omnidirectional laser bar code symbol reader (e.g. Metrologic MS 6720 Laser Scanner) 36, modified with handle 36A, for reading UPC (and other types of) symbols printed on products, brochures, documents and the like; an active-matrix LCD-type visual display screen 37 for viewing product related information automatically displayed thereon in response to the entry of the UPC numbers scanned into the UPC Number Entry Window 21D displayed on the client subsystem; a touch-screen type keyboard and pointing device 38 for clicking on anchored links on Web pages, entering information into client subsystem during its use; audio-speakers 39A for supporting multimedia Web-site that may be visited when using the client subsystem; a color or black/white printer for printer 39B for printing out Web pages under consumer command during an information finding session using the system; a scanner support stand 40 with Java GUIde flanges 41A and 41B, for Java GUIdably receiving and supporting the scanner 36 as shown in FIG. 3A3; a recoilable scanner cable 42, dispensed from cable cartridge 43 and Java GUIded through hole 44 in a scanner support bridge 40; a telephone handset 45 and associated communication apparatus for making telephone calls over a public telecommunications switching network (PSTN) independent of the operation of the Web-browser of the kiosk; and a mag-stripe card reader 46 and associated credit transaction terminal for automatically dialing up consumer credit and like databases over the PSTN (or Internet) upon scanning mag-stripe card 47 through reader 46. Optionally, the kiosk may also include one or more floppy-disc (or otherwise removable) drive units (not shown) accessible to the consumer for recording promotional and trial versions of information-based consumer products (e.g. video an audio recordings, computer software products, and the like) on removable information storage media (e.g. 1.44 MB floppy discs, 100 MB Zip® floppy discs, 1 GB Jazz® floppy discs, etc.) supplied by either the retailer or a consumer. Also, the kiosk can be provided with a stereoscopic micropolarizing LCD panel from VRex, Inc. of Elmsford, N.Y. so that micropolarized spatially-multiplexed images (SMIs) of 3-D objects represented with VRML-encoded Web pages can be stereoscopically perceived by consumers when viewed through either an electrically-passive polarizing visor structure supported from the housing of the kiosk, or a pair of polarizing eyeglasses tethered to the kiosk housing and donned by the consumer. Notably, by virtue of its compact size and low power requirements, this Web-based kiosk can be easily located in supermarkets, department stores, superstores, home-centers, discount retail outlets, or any other public location where consumer-products are being sold, offered for sale, and/or serviced.

As shown in FIG. 3A3, the bar code symbol reader is supported within its support stand/bridge 40. In this configuration, the laser scanning field of the reader is projected downwardly upon the surface of the LCD touch screen display panel. By virtue of the angle of tilt of the display panel 37 relative to the ground surface of the retail store, and the projection angle of the laser scanning field relative to the display panel surface, the consumer will be able to easy read the bar code symbol on most consumer products by simply presenting the bar code symbol to the scanning window. In the event that the product is too large to lift from the floor to the scanning window, the consumer can simply remove the bar code symbol reader 36 from its support stand 40, as shown in FIG. 3A3′, by pulling cord 42 out of its take-up compartment 43 so that the reader is positioned to read the bar code symbol 49 on the retail consumer product 48. When symbol scanning is completed, the bar code symbol reader is lifted back into its stand support position, between support Java GUIdes 41A and 41B, while the cord 42 is automatically recoiled back into storage compartment 43, as shown in FIG. 3A3. While the consumer uses the kiosk to scan UPC (or UPC/EAN) symbols on products, to find, access and display consumer product-related information on the display panel 37, he or she may choose or need to use telephone 45 to speak with a manufacturer's representative and engage in electronic commerce, and/or use the magstripe card reader 46 to read magstripe cards (e.g. credit cards) to pay for consumer purchases made over the Internet using the kiosk of the present invention.

As shown in FIG. 3A4, the Web-enabled kiosk of FIG. 3A3 is modified to include a bar code symbol reader having a “cordless-type” scanner interface, thereby eliminating the need for the communication/scanner cable 42 shown in FIG. 3A3. RF-based wireless interfaces, as disclosed in US Letters Patents and Published International Patent Applications, incorporated herein by reference, can be used to realize this cordless-type scanner interface arranged between the bar code symbol reader 36 and the Web-enabled access terminal integrated within the information kiosk. In all other respects, the kiosk shown in FIGS. 3A4 and 3A4′ is similar to the kiosk shown in FIGS. 3A3 and 3A3′ and described above.

In FIG. 3A5, a fifth illustrative embodiment of the client computer system hereof is realized in the form of a consumer product information access terminal integrated within a point-of-sale (POS) station in retail shopping environments. While this embodiment of the client computer system hereof is particularly adapted for use by sales clerks at POS stations, as well as by store employees behind retail information/service counters, it may also be used by consumers and shoppers alike provided the necessary accommodations are made as described hereinbelow.

As shown in FIG. 3A5, a client subsystem 13 hereof is realized as consumer product information access terminal 60 comprising: a POS station 61 having a cash register computer 61A and keyboard 61B, and a price/UPC Database 61C containing price and UPC number information tables; a Web-enabled computer terminal 62 connecting the POS station 61 to the Internet infrastructure 10 through an ISP 10A; a bar code symbol reader 63 connected to the POS station 61; a 15′ diagonal active-matrix LCD panel 64, operably connected to the output of the Web-enabled computer system 62 and the output of the cash register computer 61A, and having a swivel-base 65 that allows the LCD panel to be oriented in various viewing positions for displaying consumer product-related information accessed from the IPI Registrant Database shown in FIGS. 4A1 and 4A2, as well as price information accessed from the price/UPC database 61C. The advantage of this client computer subsystem is that it enables a retail sales clerk to check out customer purchases in a conventional manner, and conveniently access the IPI Finding and Serving Subsystem when check-out business is relatively slow, to answer any questions that consumers may have regarding a particular product in the retail store. This system will be ideal in retail environments having a high level of customer service and large retail service staff. In such instances, the IPI Finding and Serving Subsystem hereof empowers retail sales clerks, at the POS counters as well as customer service counters, by enabling them to quickly access any item of product related information linked to products in their stores by manufacturers and their agents.

As taught in the Objects and Summary of the Present Invention set forth hereinabove, the client computer system of the present invention 13 may also be realized in the form of a transportable bar code driven multi-media kiosk which is completely transportable within the store by hand for the convenience of consumers in retail shopping environments as shown in FIG. 3A6. As taught hereinabove, the retail shopping environment may be a department store, supermarket, superstore, retail outlet or the like. Notably, the transportable bar code driven multi-media kiosk shown in FIG. 3A6 is similar to the bar code driven multi-media kiosk shown in FIG. 3A3, except that the kiosk shown in FIG. 3A6 is scaled down in size and reduced in weight to enable the device to be completely transportable within the store by the hand of the shopper, as taught hereinabove. As shown in FIG. 3A6, the communication connection between the transportable kiosk hereof and the infrastructure of the Internet 10A can be realized using wireless digital communication technology (e.g. RF-based communication subsystems, using DFSK or spread-spectrum modulation techniques) well known in the art in order to provide (i) transportability with retail shopping environments for the convenience of shoppers, as well as (ii) Internet access to the IPI Web-site of the present invention (i.e. hosted on mirrored IPD Servers 11).

As taught in the Objects and Summary of the Present Invention set forth hereinabove, the client computer system of the present invention 13 may also be realized in the form of a bar code driven multi-media kiosk mounted upon a conventional shopping cart, or other transportation vehicle, so as to be completely transportable within retail shopping environments for the convenience of consumers, as shown in FIG. 3A7. As taught hereinabove, the retail shopping environment may be a department store, supermarket, superstore, retail outlet or the like. Notably, the bar code driven shopping cart kiosk shown in FIG. 3A7 is similar to the bar code driven multi-media kiosk shown in FIG. 3A3, except that the kiosk shown in FIG. 3A7 is mounted upon a conventional shopping cart to be completely transportable within the store, as taught hereinabove. As shown in FIG. 3A7, each shopping cart supported kiosk hereof comprises a cart structure 90 having a basket portion, a push-type handle bar portion 92, a set of wheels and a kiosk device 13 mounted to the handle bar portion. In this illustrative embodiment, the client computer subsystem embodied within the kiosk includes a 2-way RF communication link with its I/O port and a network hub associated with an IP network mounted within the retail shopping environment of concern. A wireless spread-spectrum communication subsystem including base station 98 and network adapter cards, such as the Symbol Spectrum 24 wireless LAN by Symbol Technologies, Inc. can be used to realize the 2-Way RF communication link in a manner known in the communications network art. Such a wireless LAN provides (i) transportability with retail shopping environments for convenience of shoppers, as well as (ii) Internet access to the IPI Web-sites of the present invention (i.e. hosted on mirrored IPD Servers 11). By strategically placing the access points within the retail environment, the Symbol Spectrum 24 wireless LAN makes it possible to create a wireless bridge between a wired (IP-based) LAN within the retail environment (operably connected to the Internet by an ISP) and any number of shopping cart supported kiosks, as well as fixed mounted kiosks, and transportable Internet access terminals lent to consumers for use within the retail shopping environment.

In alternative embodiments, any Client Computer 13 can be realized as a network computer (NC), a Web-TV™ type Internet Terminal, a Newton MessagePad® PDA, or any other device providing Internet access to the IPI Web-site (i.e. mirrored IPD Servers) of the present invention. Notably, the same functionalities provided within the Web-based kiosk described above can be embodied with such alternative embodiments of client computer system.

For example, as shown in FIG. 3A8, the client computer subsystem 13 can be realized as a transportable hand-held computer, such as the Newton® Model 130 Messagepad 70 from Apple Computer, Inc. of Cupertino, Calif., provided with NetHopper™ brand Internet Access (http-client) Software which supports the TCP/IP networking protocol within the Newton MessagePad operating system, as well as the client-side of http, as taught in U.S. Pat. No. 5,905,251 incorporated herein by reference. Notably, the NetHopper™ brand Internet Access (http-client) Software 71 provides the Newton Model 130 Messagepad with an integrated JAVA GUI-based web browser program for WWW access in a manner know in the Internet access art. As shown in FIG. 3A8, the Newton Messagepad has a display panel 72, touch-screen type keypad 73, and programmed laser scanning bar code symbol reader 74 (e.g., Metrologic ScanQuest® Laser Scanning Module Model No. IS4120), integrated within the hand-held device as described in U.S. Pat. No. 5,905,251. The function of bar code symbol scanner 74 is to read UPC or UPC/EAN symbols on consumer products and to produce symbol character data representative of the numbers encoded within such standardized bar code structures. The Newton Messagepad Model 130, mdenoted by reference numeral 70, is also equipped with a Motorola PCMCIA-based modem card 75 having a RF transceiver for establishing a wireless digital communication link with either a cellular base station or one or more satellite-base stations 76 connected to the Internet by way of an ISP or NSP 10A in a manner well known in the global information networking art. As such, a first wireless digital communication link 77 is established between the Newton Messagepad 130 and cellular (or satellite) base stations 76, and a second digital communications link 78 is established between the base station 76 and the ISP or NSP associated with the infrastructure of the Internet. Accordingly, this embodiment of the client computer subsystem of the present invention is completely mobile (i.e. transportable and provide the consumer access to the Internet and all of its information resources on the WWW and elsewhere, provided that the device maintains its wireless digital communication link with base station 76, distributed through the globe, making access to the IPD servers hereof possible at home, in the office, within retail stores, as well as on the road wherever that may be.

As shown in FIG. 3A8, the Newton MessagePad, ScanQuest® Laser Scanning Module 74 and auxiliary battery supply (not shown) are completely housed within a rubberized shock-proof housing 79, in order to provide a hand-supportable unitary device 70 of rugged construction. This hand-held Internet-enabled wireless information access terminal can be used virtually anywhere, provided wireless Internet access is enabled by digital IP communication network service providers (NSPs) in operation about the planet. Operation of Internet access terminal 70 is quite simple from the user's point of view. Upon reading a bar code symbol 80 on a consumer product 81, the object detection field 82 of the device automatically detects the consumer product, and in response thereto, a laser beam 83 is automatically projected and swept across the UPC symbol 80 thereon. While it is generally preferred that the automatic laser scanning engine 74 be interfaced with I/O communications port of the Newton MessagePad device 70, it is understood that, in some instances, it may be desired to connect a pen or wand-type scanning device to the serial port thereof to provide bar code symbol reading capabilities thereto. Optionally, bar code decoding software can be run on the Message Pad device, or as firmware contained within the scanning engine 74 in a manner known in the art.

Notably, it is understood that there will be many different types of wireless mobile Internet-enabled access terminals that may be used to realize the client computer subsystems of the present invention. For example, recently 3COM, Inc. introduced into its commercial product line the PalmPilot VII Wireless Hand-Held Internet Access Terminal, which is similar in many respects to the Newton Messagepad Model 130 equipped with the Motorola PCMCIA-based modem card 75, and Nethopper™ Software, described above. Also, Symbol Technologies, Inc. of Holtsville, N.Y. has introduced the Symbol SPT 1500, SPT 1700, SPT 1740 and PPT 2700 hand-held wireless bar code scanning Internet access terminals which have virtually the same functionalities embodied within the wireless hand-held Internet access terminal shown in FIG. 3A8, and originally disclosed in U.S. Pat. No. 5,905,251, supra.

The Web-enabled client subsystems 13 of the present invention described hereinabove may be used to access consumer product-related information, as well as to carry out electronic-commerce related transactions, at home, at work, in the office, on the road, as well as in physical retail shopping environments.

For example, when visiting particular EC-oriented (i.e. electronic-commerce enabled) Web-sites, a consumer may scan UPC (and/or UPC/EAN) numbers on products within his or her home (e.g. in the pantry) using any one of the client computer subsystems hereof equipped with a bar code symbol Reader in order to remotely purchase such consumer products using credit or debit type financing, and direct shipment of purchased products to the consumer's home or elsewhere by a particular delivery service. Such EC-enabled WWW sites, commonly referred to as electronic-commerce (EC) stores or storefronts, as well as on-line electronic commerce catalogues, can be operated by manufacturers, wholesalers and/or retailers of consumer products, as indicated in FIGS. 2-1 and 2-2. As shown therein, retailer operated, managed and/or owned EC stores (i.e. EC-enabled WWW sites) are hosted on retailer operated/owned EC information servers (MECIS) 12B, whereas manufacturer operated, managed and/or owned EC stores (i.e. EC-enabled WWW sites) are hosted on manufacturer operated/owned EC information servers (MECIS) 12B operably connected to the infrastructure of the Internet.

The consumer product information delivery system of the present invention shall enable an infinite array of applications with regard to electronic commerce and home shopping, now made possible by the present invention.

The Database Structure of the IPD Server

In the illustrative embodiment of the present invention, each data-synchronized IPD Server 11 of the preferred embodiment maintains at least two different relational-type databases, namely: a IPI Registrant Database for storing information about manufacturers whose products are registered with the system; and a Non-IPI Registrant Database for storing information about manufacturers whose products are not registered with the system. A schematic representation of the IPI Registrant Database is shown in FIG. 4A1, whereas a schematic representation of the Non-IPI Registrant Database is shown in FIG. 4B.

As shown in FIG. 4A1, the relational-type IPI Registrant Database maintained by each IPD Server comprises a plurality of labeled information fields for each product “registered” therewith, namely: an IPN Information Field for storing information (e.g. numeric or alphanumeric string) representative of the Universal Product Number (e.g. twelve-digit UPC Version A number, eight-digit UPC Version E number, thirteen-digit UPC/EAN number, or twelve-digit UPC Version A number plus five-digit Add-On Code Segment number frequently used in the publishing industry) assigned to the consumer product; a Company Name Information Field for storing information (e.g. numeric or alphanumeric string) representative of the name of the company making, selling or distributing the corresponding product; a URL Information Field(s) for storing information (e.g. numeric or alphanumeric string) representative of the Universal Resource Locator (URL) or Universal Resource Locators (URLs) at which information resource(s) of the multimedia type can be found on the Internet relating to the corresponding consumer product; a Trademark Information Field for storing information (e.g. text and/or alphanumeric strings) representative of each trademark (or Domain Name) used in connection with the promotion, sale, distribution and/or use of the corresponding product, and preferably registered with the United States Patent and Trademark Office (USPTO) or other governmental or quasi-governmental agency (e.g. INTERNIC or Network Solutions, Inc.); a Product Description Information Field for storing information (e.g. text strings) descriptive of the corresponding product; an E-mail Address Information Field for storing information (e.g. numeric or alphanumeric string) representative of the e-mail address of the corresponding company (e.g. manufacturer) on the Internet; a CPIR-Enabling Applet Information Field for storing information representative of consumer product information request (CPIR) enabling Applets accessible by retailers, wholesalers, advertisers, Web publishers and the like by downloading operations to be described in detail hereinafter, and eventually inserted within the HTML code of Web documents on various types of Internet information servers used to host WWW sites of all sorts, so that, when executed, these CPIR-enabling Applets automatically access from the master UPN/URL Database Management Subsystem 9 hereof, a categorized menu of URLs specifying the location of information resources on the Internet pertaining to a particular UPN-labeled product and symbolically linked thereto by its manufacturer or authorized agent; image file storage field for storing color images of consumer products registered with the system; and a Status Information Field for storing information (e.g. numeric or alphanumeric string) representative of whether the company (e.g. manufacturer) associated registered product has paid their monthly, quarterly or annual registration fees associated with registration within the IPD Servers of the information finding and serving subsystem hereof. Notably, each information item contained with the information field shown along the same horizontal line of FIG. 4A1 is related or linked.

In general, the URL stored in the URL Information Field specifies the address of an information resource on the Internet (e.g. Web), and thus may point to any one of the following types of information resources: a HTML document or file on the World Wide Web (expressed in the HyperText Markup Language); a single record in a database; the front-end of an Internet program such as Gopher; or the results of a query made using another program. In accordance with convention, the syntactic structure of each URL generally comprises: a Protocol Specifier, such as “http”, “ftp”, “gopher”, “news”, or “mail to”, and specifies the type of resource that the URL is pointing (i.e. connecting) to; a Host Indicator, represented by double slashes “//” if the URL is requesting information from a Web Server; Server Name comprising an Internet Domain Name (e.g. “www.”), the address of the Web Server (e.g. “ibm.”), and a designator (e.g. “com”, “edu”, “int”, “mil”, “net”, “org”, etc.) identifying who owns the server or where it is located; a Path Name, such as “Products/Computers/”, indicating a path to the destination information file on the identified Server; and a Resource Name (including file extension, e.g. “.html”), such as “aptiva.html”, identifying the actual named information file that contains actual information resource specified by the URL.

As used herein as well as in the Claims to Invention, the term “registered” and the variants thereof shall be understood to mean listed or having an entry within a database. Such listing or entry can be achieved in a variety of ways including, but not limited to: (i) by specific request of the associated company or business; or (ii) by the system administrator without a request and/or authorization of the corresponding company or business linked to the product.

Notably, each information item contained within the information field shown along the same horizontal line of FIG. 4A1 is symbolically related or linked. Different products of the same registrant or related registrant may also be linked together so that a user looking for information about a particular product is automatically provided with URLs which are assigned to related products of the registrant which may satisfy the goals or objectives of a particular advertising and/or marketing campaign or product promotion program of the registrant company. As it may be desired to relate particular products at particular points in time, the relationships therebetween can be dynamically changed within the IPI Registrant Database by a straightforward database updating operation carried out by a system administrator (or manager) who, in theory, can be located virtually anywhere throughout the world. Expectedly, such database updating operations would be carried out using appropriate system access and security procedures well known in the art.

Inasmuch as the UPC data structure is presently employed as a universal product identifier (i.e. a primary data structure) in a majority of industries throughout the world, its twelve-digit numeric string (for UPC Version A) or eight-digit numeric string (for UPC Version E) will be a preferred UPN (in many applications) for purposes of carrying out the principles of the present invention. This twelve (12) digit human-readable number, printed on the bottom of each UPC label (and encoded within the bars and spaces of the UPC label itself), comprises: (i) a six digit manufacturer number assigned to the manufacturer by the Uniform Code Council, Inc. (UCC) of Dayton, Ohio, and consisting of a one digit “number system” number and a five digit manufacturer code; (ii) a five digit “product” number assigned to the product by the manufacturer; and (iii) a one digit modulo check digit (mathematically calculated) and added to each UPC number to check that the code has been read correctly by the bar code symbol reader.

In order to provide the requester greater control over what information is actually displayed on its client subsystem, the URL Information Field of the IPI Database shown in FIG. 4A1 contains a number of information subfields. As shown in FIG. 4A2, these information subfields comprise: a Product Advertisement Information Field for storing information representative of URLs pointing to information on the Internet relating to advertising and/or promotion of the product; a Product Specification (i.e. Description) Information Field for storing information representative of URLs pointing to information on the Internet relating to specifications on the product; a Product Update Information Field for storing information representative of URLs pointing to information on the Internet relating to product updates, recalls, notices, etc; a Product Distributor (e.g. Wholesaler and/or Resaler) Information Field for storing information representative of URLs pointing to information on the Internet relating to distribution, sale and/or ordering of the product; a Product Warranty/Servicing Information Field for storing information representative of URLs pointing to information on the Internet relating to warranty, extended warranty offerings, servicing and maintenance of the product; a Product Incentive Information Field (e.g. rebates, discounts and/or coupons) for storing information representative of URLs pointing to information on the Internet relating to rebates, discounts and sales on the product; a Product Review Information Field for storing information representative of URLs pointing to information on the Internet relating to reviews, analysis, testing, inspection and/or comparison of the product; and Miscellaneous Information Field(s) for storing information representative of URLs pointing to information on the Internet relating to miscellaneous aspects of the product (e.g., direct product sales on the WWW, product installation/set-up and operating manuals, company reports (10Ks, annual reports, etc.), and the like. Each URL symbolically linked to a UPC-labeled product registered in the Registered IPI Database is categorized within one or more of these URL categories.

The list of URLs recordable in the IPI Registrant Database for each registered UPC-labeled product is virtually unlimited. Below are just a few examples of how the IPI Finding and Serving Subsystem hereof can be used as a virtual sales agent that provides value-added services to consumers, retailers and the like.

For each CD sound recording, the URL list may contain a URL that points to a promotional QuickTime® video recording or MP3-formatted sound recording published on the WWW for reviewing and evaluation by the consumer. The promotional song can be by a commissioned or endorsing artist, as is typically done in conventional advertising programs. The same can be done for video recordings on tape and digital video discs (DVDs). The URL may also provide the consumer with a down-loadable trial version of the product for a limited time period.

For each computer software product, the URL list may contain a URL that points to a multi-media clip on the WWW that provides a demonstration of the solutions that the software product provides, as well as the functions and development tools that it enables. It may also provide the consumer with a down-loadable version of the software product for a time-limited trial period.

For electronic consumer products, the URL list may contain a URL that points to a multi-media clip on the WWW that provides an audio-visual demonstration of the product in various user environments. Also, the URL can contain a URL that points to a Web-based Specification Sheet that can be printed out in a retail environment, at home, work or on the road.

For groceries and like articles, the URL list may contain a URL that points to a multi-media clip on the WWW that provides a QuickTime® video recording or the like of the product, illustrating various cooking recipes and uses for the product. Also, the URL list can contain a URL that points to a Web-based Discount Coupon that can printed out in the store, at home or work.

For toys, the URL list may contain a URL that points to a multi-media clip on the WWW that provides an audio-visual demonstration of the toy along with promotional endorsements by the various characters used in its advertising campaign.

For clothing, garments, or accessories (e.g. wearing apparel), the URL list may contain a URL that points to a multi-media clip on the WWW that provides a QuickTime® video recording or the like of the clothing, garments, and/or accessories being modeled by stunning fashion models. Ideally, such video recordings, linked to particular articles of wearing apparel by their UPC number, can be used to extend and augment the advertising campaign being carried out in other forms of media (e.g. television, radio, print, billboards, etc.).

Preferably, the manufacturer, its marketing personnel and advertising agents will actively participate in the creation of the product related information resources, as well as the placement of their URLs into the above-defined (or like) URL categories maintained within the Database of the IPI Finding and Serving Subsystem hereof. Also, using the Manufacturer/Product Registration Subsystem hereof, manufacturers and/or their agents can easily link their UPNs (e.g. UPC and/or EANs) with such URLs and manage the same in a dynamic manner to ensure that product related information on the Internet is accurately linked to the UPNs of the manufacturer's products. Through such active participation, the business objectives of any particular manufacturer or retailer can be promoted by way of the IPI Finding and Serving Subsystem of the present invention. In this way, the information requesting consumer is provided with only the kinds of product-related information which he or she seeks.

As shown in FIG. 4B, the Non-IPI Registrant Database maintained by each IPD Server comprises a plurality of labeled information fields for each product that is not currently registered with the IPD Server, namely: an IPSN (i.e. IPN) information Field for storing information (e.g. numeric or alphanumeric string) representative of the Universal Product Number (e.g. a UPC number from a UPC numbering system, or an EAN numbering system) assigned to the non-registered product; a Company Name Information Field for storing information (e.g. numeric or alphanumeric string) representative of the name of the company making, selling or distributing the corresponding non-registered product; a Trademark Information Field for storing information (e.g. text and/or alphanumeric strings) representative of each trademark used in connection the promotion, sale, distribution and/or use of the corresponding product, and preferably registered with the USPTO or other governmental agency; a Product Description Information Field for storing information (e.g. text strings) descriptive of the corresponding product; and an E-mail Address Information Field for storing information (e.g. numeric or alphanumeric string) representative of the e-mail address of the corresponding company (e.g. manufacturer) on the Internet; a Status Information Field for storing information (e.g. numeric or alphanumeric string) representative of whether the company associated non-registered product has been solicited by the IPD Server, and on what dates registration solicitation has occurred. Notably, each information item contained with the information field shown along the same horizontal line of FIG. 4A1 is related or linked. The information required to construct the Non-IPI Registrant Database shown in FIG. 4B can be readily obtained from a number of commercially or publicly available information sources (e.g., the Universal Code Council, Inc., Dayton, Ohio; QRS, Inc. Of Richmond. Calif.; General Electric Information Services (GEIS) of Delaware, Md.; etc.).

Constructing the IPI Registrant Datahase Within the TPI Finding and Serving Subsystem Hereof

The utility of the product finding functionalities of the IPI Finding and Serving Subsystem hereof depends in large part on the number of consumer-products registered with the IPI and Non-IPI Registrant Databases supported within the UPN/URL Database Management Subsystem 9 hereof, as illustrated in FIGS. 2B1, 2B2, 2B3 and 2B4. In principle, numerous techniques may be employed separately or in combination with each other in order to construct the IPI and Non-IPI Registrant Databases of the present invention. Six such techniques will be detailed below.

According to a first database construction technique, the administrator of the IPI Registrant Database would transmit Product Registration Requests (PRRs) in the form of electronic documents to each and every the manufacturer having been issued, for example, a six digit UPC Manufacturer Identification Number (MIN) by the UCC, Inc. Such electronic documents can be transmitted using conventional MIME protocols such as, for example, STMP. The Product Registration Request document would seek to ascertain from the manufacturers the various information items (including the menu of URLs) identified in the IPI Registrant Database of FIG. 4A1. In response to the Product Registration Request, each solicited manufacturer would send back to the administrator of the IPI Registrant Database (for each of its consumer products) its UPC number and a menu of catagorized URLs indicating the location of the information resources identified in the Product Registration Request document. This information can then be used to readily construct the IPI Registrant Database of the illustrative embodiment.

According to a second database construction technique, a global advertising campaign would launched (over various media) in order to solicit the various information elements identified in the IPI Registrant Database of FIG. 4A1 and thus register the products of the manufacturers selling UPC-labeled products. Preferably, such information would be collected by way of an electronic data transfer subsystem(s) set-up to cooperate with the system of the present invention in order to facilitate database construction operations.

According to a third database construction technique, the IPI system itself would continuously solicit consumer product registrations over time in order to collect information from companies responding favorably to the solicitations. While such solicitation efforts can involve the issuance of product registration requests using various types of media, it is preferred that the information collection operations are carried out using electronic data transfer techniques (e.g. ftp, EDI or XML/ICE) described hereinabove.

According to a fourth database construction technique, a number of commercial on-line Internet search engines, such as AltaVista™, Yahoo™, WebCrawler™, Lycos™, Excite™, as well as powerful off-line parallel-processing search engines, would be enlisted to analyze (i.e. mine) information on the WWW in order to collect and link the information elements specified in the IPI Registrant Database of FIG. 4A1.

Once an “initial” IPI Registrant Database has been constructed using any one or more of the four database construction techniques described hereinabove, manufacturers registered therewith can be periodically contacted using Web-based electronic document (i.e. message) transfer techniques in order to request updating and confirmation of the UPN/URL listings contained within the database of the IPI subsystem of the present invention.

According to a fifth database and preferred construction technique of the present invention, the Registrant IPI Database of the system would be initially “seeded” with several items of information obtained and related without the assistance of manufacturers of UPC-labeled products. Such information items include: (1) the six digit UPC Manufacturer Identification Numbers encoded in the UPC symbols (and numbers) applied to the products of such UCC-registered manufacturers; and (2) the URLs of the Web home pages of such manufacturers.

The first step of this database construction method involves obtaining the six digit Manufacturer Identification Numbers (MINs) uniquely issued to manufacturers by the Uniform Code Council, Inc. of Dayton, Ohio. Such MINs can be obtained from various commercial sources including GE Information Services, QRS, Inc. formerly Quick Response Services, Inc.), as well as the UCC. At present, about 180,000 Manufacturers Identification Numbers have been issued to manufacturers by the UCC. A string of six zeros (i.e. 000000) may be added to each one of these 180,000 or so six digit Manufacturer Identification Numbers in order to produce 180,000 or so 12 digit numbers (i.e. hereinafter referred to as “Manufacturer's Reference Numbers) for the 180,000 or so manufacturers listed in the IPI Registrant Database under construction. As each such Manufacturer Reference Number has the same length as a UPC number of its manufacturer, this number can be conveniently thought of as the “Manufacturer Reference UPC Number” which can be stored in the UPN Information Field of the Database along with the corresponding manufacturers name being stored in the Company Name Information Field.

The second step of the method involves finding the URL of the Web home page of each of the 180,000 manufacturers who have been assigned a Manufacturers Identification Code and are listed in the Database. Such URL information can be found using a number of available techniques: (i) using a Commercially available search engine to search the WWW in order to find the URL of the home page of each manufacturer's Web-site, if it has one, using the name and address thereof obtained during the first step above; or (ii) using a commercially available (INTERNIC-enabled) Domain Name search service that uses the names and addresses of the manufacturers (obtained during the first step above) in order to determine whether a particular manufacturer has a registered domain name on the Internet, and if so, is the domain name being actively used in a URL that points to the home page of the manufacturer's Web-site. Once obtained, such URLs are then added to the IPI Database, along with the e-mail and/or other address of the manufacturer symbolically linked thereto (if available).

Having constructed the “seeded” Database, it can then be used to connect the client subsystem of users to the home page of Web-sites of manufacturers of particular products. Initially, when an Internet user provides the UPC number of a particular product as input to the Input Box of the HTML form displayed in the information display frame of the client subsystem (e.g. when operated in its Manufacturer Website Search Mode), then the IPD Server need only compare the first six digits of the entered UPC number against the first six-digits of the Manufacturer Reference UPC Numbers (i.e. Manufacture Identification Numbers) listed in the “seeded” Database. The corresponding (home-page) URL of the matching manufacturer is returned to the client subsystem Ca for display. In instances of an initially seeded Database, in which only the “Manufacturer Reference UPC Numbers” are listed therein, the requesting client subsystems are provided with the URLs of the home pages of the symbolically linked manufacturers. Then as manufacturers begin to register their consumer products with the system (e.g. in response to mass e-mailings, advertisements and/or marketing and promotional efforts, etc.), the IPD Database will return a menu of “hot-linked” URLs, for each registered product, pointing to various types of product-related information resources on the Internet (described above) that can be easily accessed by simply clicking thereon in a conventional manner. Over time, Manufacturer Reference UPC Numbers and the URLs of the “home pages” of such manufacturers will become replaced by the UPC numbers of registered products and the menu of URLs on the WWW symbolically linked thereto by the manufacturers, thereby allowing consumers and users of the system to precisely pinpoint consumer product-related information on the WWW which has been specified by the manufacturer, its marketing department and/or advertising agency. With manufacturer's and advertiser's participation and feedback, the initially seeded RDBMS described hereinabove will quickly grow into a robust RDBMS richly filled with the various information items described in FIGS. 4A1 and 4A2, including the symbolically linked UPCs and URLs that point to very specific consumer product related information resources (i.e. files) stored within IPI Servers of the system located across the global expanse of the Internet.

According to a sixth database construction technique of the present invention, the Registrant IPI Database of the system would be constructed by allowing each manufacturer to construct a limited or restricted version of the master UPN/URL Database (i.e. Registrant IPI Database) of the system, wherein only UPC-encoded products of the registered manufacturer and Web-based information items related thereto are entered into the database. As will be described in greater detail herebelow in connection with the third method of Product Registration in the subsystem hereof, the creation of such limited-version UPN/URL databases can be carried out by providing each registered manufacturer with a computer program that allows its administrators to construct and manage a limited UPN/URL database in a “turn-key” manner. Also, from its Website, the manufacturer can serve the limited UPN/URL database over the Internet to consumers. As part of the registration process, each registered manufacturer transmits its limited UPNIURL database to Web-server 30 which then integrates all such databases in order to update the master UPN/URL database (IPI Registrant Database) of the system.

Methods of Constructing UPN-Encoded Server-Side and Client Side Applets and Distributing the HMTL Tags Associated Therewith to Remote Client Subsystems for Embedding Within HTML-Encoded Documents to be Published Over the Internet in Connection with UPN-Labeled Consumer Products

In general, for each system architecture shown in FIGS. 2B1 through 2B4, there will be a different Applet-driven method used to access consumer product related information (e.g. UPN/URL links) from the RDBMS server 9 and display the search results within a Java-based GUI at the point of presence of the consumer using a Java-enabled client machine 13. In order to practice these different methods, it will necessary construct either server-side or client-side UPN-encoded CPIR-enabling Applets, distribute the HTML tags associated therewith to remote client subsystems, and thereafter embed these CPIR-enabling Applet tags within HTML-encoded documents for publishing over the Internet. Such CPIR-enabling Applet construction, distribution and embedding methods will now be described in detail hereinbelow.

The First Applet-Driven Method of Accessing and Displaying Categorized UPN/URL Link Menus from the UPN/URL Database Management Subsystem the Present Invention

After providing a brief overview on the system architecture of FIG. 2B1 and the nature of the server-side CPIR-enabling Applets deployed therewithin, The steps associated with Applet-driven CPI-acquisition method of the first illustrative embodiment will be described in detail with reference to FIGS. 4E1, 4E2, 4F1 and 4F2.

In general, the method of FIGS. 4E1 and 4E2 involves using a server-side CPIR-enabling Applet to automatically conduct a UPN-directed search on the UPN/URL Database Management Subsystem 9 hereof (i.e. RDBMS server 9) in response to a single mouse-clicking operation by the consumer on the HTML tag associated with the server-side Applet. In the illustrative embodiment, the CPIR-enabling servlet of the present invention is a program written in the Java™ programming language and has an HTML tag (indicated by <SERVLET>) which is designed to be included in an HTML page, much in the same way an image can be included therewithin (according to the HTML 3.2 Specification).

CPIR-enabling servlets of the present invention are designed to work within a request/response processing model, as shown in FIG. 2B1. In this request/response model, a client subsystem 13 sends a request message to the Java Web Server 11′ and the Server 11′ responds by sending back a reply message. In the illustrative embodiment, requests come in the form of http, although is understood that the use of other protocols such as ftp, EDI or a custom protocol, may be possible in particular embodiments. The request and the corresponding response reflect the state of the client and the server at the time of the request.

When using a Java-enabled browser to view a Web page containing a server-side CPIR-enabling Applet tag <SERVLET>, the servlet's compiled class code is automatically accessed from the Java Web Server 11′ and executed on the server-side of the network connection illustrated in FIG. 2B1. Thus, as shown in FIG. 2B1, the Java Web Server 11′ must provide a Java Virtual Machine (JVM) for running/executing Java servlets on the server-side of the network in much the same way that a client browser must provide a JVM for running Java Applets on the client side thereof. Additionally, the Java Web browser 11′ must also support the Java Servlet API, developed by JavaSoft, and define how and when the servlet communicates with the Java Web Server. Essentially, the Servlet API is a well-defined set of function calls (i.e. set of Java classes) to get information to and from the Java Web Server. The servlet needs to be able to access server-defined variables, issue redirects, send error messages and the like. Sun's Java Web Server supports the Servlet API and, of course, includes their JVM.

As shown in FIG. 2B1, the Java Web Server 11′ includes a number of software components including the Java Servlet API which comprises several Java interfaces and fully defines the link between the hosting server (e.g. Java Web Server) and the servlets located at the middle tier. The Servlet API is defined as an extension to the standard JDK. This means that there is an explicit definition of servlet interfaces, but it is not part of the Java Development Kit (JDK) 1.1 or the Java 2 platform. Instead, the servlet classes are delivered with the Java Servlet Development Kit (JSDK) version 2.0 from Sun (http://java.sun.com/products/servlet/). This JSDK version is intended for use with both JDK 1.1 and the Java 2 platform. There are a few significant differences between JSDK 2.0 and JSDK 1.0.

JDK extensions are packaged under javax--the root of the Java extension library tree. The Java Servlet API contains the following packages: Package javax.servlet; and Package javax.servlet.http dedicated to supporting HTTP protocol and HTML generation. The Servlet API provides a tight link between a server and servlets, allowing servlets to add new protocol support to a server. Essentially, any protocol (e.g. SMTP, POP, FFP, etc.) that follows a request/response computing model can be implemented by a servlet.

General servlet support is provided by the package “javax.servlet” which comprises the following components:

-   (1) Servlet: An interface that defines communication between a web     server and a servlet. This interface defines the init( ), service(     ), and destroy( ) methods (and a few others). -   (2) ServletConfig An interface that describes the configuration     parameters for a servlet. This is passed to the servlet when the web     server calls its init( ) method. Note that the servlet should save     the reference to the ServletConfig object, and define a     getServletConfig( ) method to return it when asked. This interface     defines how to get the initialization parameters for the and the     context under which the servlet is running. -   (3) ServletContext: An interface that describes how a servlet can     get information about the server in which it is running. It can be     retrieved via the getServletContext( ) method of the ServletConfig     object. -   (4) ServletRequest: An interface that describes how to get     information about a client request. -   (5) ServletResponse: An interface that describes how to pass     information back to the client. -   (6) GenericServlet: A base servlet implementation. It takes care of     saving the ServletConfig object reference, and provides several     methods that delegate their functionality to the ServletConfig     object. It also provides a dummy implementation for init( ) and     destroy( ). -   (7) ServletInputStream: A subclass of InputStream used for reading     the data part of a client's request. It adds a readLine( ) method     for convenience. -   (8) ServletOutputStream: An OutputStream to which responses for the     client are written. -   (9) ServletException: Should be thrown when a servlet problem is     encountered. -   (10) UnavailableException: Should be thrown when the servlet is     unavailable for some reason.

Support for HTTP Servlets is provided by the package “javax.servlet.http” which comprises the following components:

-   (1) HttpServletRequest: A subclass of ServletRequest that defines     several methods that parse HTTP request headers. -   (2) HttpServletResponse: A subclass of ServletResponse that provides     access and interpretation of HTTP status codes and header     information. -   (3) HttpServlet: A subclass of GenericServlet that provides     automatic separation of HTTP request by method type. For example, an     HTTP GET request will be processed by the service( ) method and     passed to a doGet( ) method. -   (4) HttpUtils: A class that provides assistance for parsing HTTP GET     and POST requests.     The central abstraction in the Java Servlet API is the Servlet     interface. All servlets implement this interface, either directly or     more commonly by extending a class that implements it (e.g. such as     the HttpServlet class). The Servlet interface declares but does not     implement methods that manage the servlet and its communication with     clients. The servlet writer will provide some or all of these     methods when developing a CPIR-enabling servlet.

Having provided an overview on server-side CPIR-enabling Java Applets (i.e. Servlets) of the present invention and the support framework required thereby in a distributed-computing object oriented programming environment shown in FIG. 2B1, it is appropriate to now describe the method of creating, loading, distributing, embedding and executing server-side CPIR-enabling Java Applets in accordance with the principles of the present invention schematically illustrated in FIGS. 4E1, 4E2, 4F1 and 4F2.

As indicated at Block A1 in FIG. 4E1, the first step of the method involves using the Java Servlet API to write or otherwise author the source code for a server-side CPIR-enabling Java Applet., for each UPN-specified consumer product registered in the UPN/URL Database Management Subsystem 9. In general, the source code for each server-side CPIR-enabling Java Applet (i.e. servlet) will embody one or more of following items of information, namely: (i) the UPN of the particular product on which the CPI search is to be carried out and the search results thereof displayed; (ii) Java classes required for performing a UPN-directed search on the RDBMS Server 9 using one or more Java methods running natively on the Java Web Server 11′, and producing a particular Java GUI for displaying the results obtained from the UPN-directed search; and (iii) license-related information specifying the terms and conditions of the CPIR-enabling Servlet license and the conditions under which the CPIR-enabling servlet shall operate.

Notably, such license-related information may specify: (1) one or more specific host domains (e.g. www.homedepot.com or www.walmart.com ) from which a Web document containing the corresponding servlet tag may launch the CPIR-enabling servlet under a licensing program; (2) one or more general Internet domains (e.g. .com, .org., .gov, .int, .mil, uk, etc.) from which a Web document containing the corresponding servlet tag may launch the CPIR-enabling servlet under a licensing program; (3) the time duration of the licensing period associated with the CPIR-enabling servlet; and (4) any other restrictions set by the associated manufacturer and/or retailer, and/or administrator of the consumer product information system hereof, that must be observed for a registered CPIR-enabled servlet to operate within a Web-document served from the registered Internet domain.

Notably, the Java source code for each CPIR-enabling Servlet will vary depending upon implementation. However, regardless of the particular implementation, it can be expected that each JDBC-supporting CPIR-enabling servlet when, for example, designed to search an (Oracle JDBC-supported) UPN/URL Database Server 11A for the UPC/URL list currently symbolically linked to a specified UPN and display the search results on the requesting client machine 13, will typically include Java source code specifying:

-   (1) the importable JDBC classes required by the CPIR-enabling     Servlet; -   (2) the importable Java classes to be used in the CPIR-enabling     Servlet; -   (3) the JDBC driver to be loaded for the Oracle-based UPN/URL     Database; -   (4) the connection strings to the UPN/URL Database; -   (5) the CPI query to be executed on the UPN/URL Database, dependent     on the UPN of the associated consumer product and possibly other     search criteria and Servlet licensing conditions; -   (6) the servlet tag, its graphical icon or alias to trigger     execution the Servlet and its associated CPI query; -   (7) the CPI Search Result GUI to be displayed on the requesting     client machine and its relative location to the associated Servlet     tag; and -   (8) the operations that will be carried out upon execution of the     CPI query including     -   Boolean search logic to be carried out upon initiation of the         UPN-directed CPI search;     -   if a new connection is required between Java Web Server and the         UPN/URL Database;     -   Loading the JDBC driver;     -   Connecting to the UPN/URL Database;     -   Creating a SQL statement based on the specified Boolean search         logic and UPN;     -   Executing the SQL query statement; and     -   Dumping the search results to the CPI Search Result GUI.

In the embodiment depicted in FIG. 2B1, a UPN-encoded Servlet is used to replace a Common Gateway Interface (CGI) script and provide a way of searching the UPN/URL Database on RDBMS Server 11′, with the advantage of increased speed and stability. In this instance, CPIR-enabling Servlets are accessed by the user as an HTML tag <SERVLET> embedded in an HTML document served to the client subsystem 13. For example, when the consumer selects the servlet tag (graphically encoded by an icon or image) in an HTML-encoded document, the linked servlet residing on the server-side of the network, is automatically executed, causing a UPN-directed search to be carried on the RDBMS server 9.

After writing/authoring the source code for the Applet, the CPIR-enabling Java servlet is ascribed a unique name such as, for example, “UPNXXXXXXYYYYYZ” for a 12 digit Uniform Product Code.

Reference can be made to the following technical publication for additional details on writing Java servlets, designing Java GUIs and the like: “Java Servlets and Serialization With RMI” (1999) by Scott McPherson, published by Sun Microsystems, Inc., of Palo Alto, Calif.; “The Java™ Tutorial Second Edition: Object Oriented Programming For The Internet” (1999), by Mary Campione and Kathy Walrath, published by Sun Microsystems, Inc., of Palo Alto, Calif.; and “The JFC Swing Tutorial: A Java Guide To Constructing JAVA GUIs” (1999), by Mary Campione and Kathy Walrath, published by Sun Microsystems, Inc., of Palo Alto, Calif.; “JAVA” (1997) by Ed Tittel and Bill Brogden, published by IDG Books Worldwide, Inc.; “Wilde's WWW: Technical Foundations of the World Wide Web” (1999) by Erik Wilde, published by Springer-Verlag, Berlin, Heidelberg each said publication being incorporated herein by reference.

As indicated at Block A2 in FIG. 4E1, the source code for the authored servlet is compiled into Java bytecode, and java bytecode for the servlet classfiles are placed in the server_root/servlets directory on the Java Web Server 11′. When compiling, the javax.servlet.* package should be placed in the classpath. The easiest way to do this is to include server_root/lib/classes.zip in the classpath, but it is understood that one must look to the compiler's documentation for specific details in this regard.

As indicated at Block B1 in FIG. 4E1, the second step of the method involves using the Java Server Administration Applet to configure the Java Web Server so as to extend the functionalities thereof and embody (or install) the CPIR-enabling Java servlet within the Java Web Server 11′. This process of extending the functionalities of the Java Web Server 11′ involves specify the default parameters and arguments thereof. This configuration step is carried out when using the Servlet Loading facility of the Administration Applet in order. The loading process is achieved by clicking on the Servlets Button, and then selecting Add from the list of choices on the left GUI of the Servlet Loading Facility. Thereafter, to add a new servlet, the following procedure is performed: Enter in the Servlet Name field, the unique name for the CPIR-enabling Java servlet one is loading onto the Java Web Server (e.g. “UPNXXXXXXYYYZ”); Enter in the Servlet Class field, a valid class name for the Java class of the CPIR-enabling servlet, i.e., the full package name, e.g. “sun.server.http.FileServlet”; and thereafter Click on the Add button.

As indicated at Block B2 in FIG. 4E1, the fourth step of the method involves invoking the CPIR-enabling Java servlet by creating a URLhaving the path section “/servlet/” prepended to the assigned Servlet Name, so that the URL can be thereafter embodied within the servlet HMTL tag <SERVLET>, prior to its insertion within the HTML code of a Web document. To invoke a servlet, the webmaster/administrator calls the servlet by creating a URL with “/servlet/” prepended to the servlet name. One can confirm that the servlet is correctly invoked by entering this URL into ones Web browser and analyzing the output of the created servlet.

As indicated at Block B3 in FIG. 4E1, the fifth step of the method involves (1) embodying the unique URL, created for each consumer product, within a CPIR-enabling servlet HTML tag <SERVLET>, (2) containing each such servlet HMTL tag within an executable file, and (3) storing each such servlet tag containing file in the Central CPIR-Enabling Applet Library on the RDBMS Server 9.

As indicated at Block C in FIG. 4E2, the sixth step of the method involves distributing the CPIR-enabling servlet HMTL tags (within the Central CPIR-enabling Applet Library) to retailers, wholesalers, advertisers, and others who desire to deliver UPN-directed CPI search results to their customers, clients and the like. This distribution process can be carried out by downloading servlet tag containing files to a remote computer system connected to the Internet using, for example, ftp or other electronic data or document interchange protocols (e.g. XML/ICE) to carry out the servlet tag transport process. These downloaded CPIR-enabling servlet tags can then be stored in a local CPIR-Enabling Applet/Servlet Library maintained on a client computer 13, as shown in FIG. 4F2, until it is time to embed the same into a particular HTML-encoded document.

As indicated at Block D in FIG. 4E2, the seventh step of the method involves enabling retailers, wholesalers, advertisers, and others to (1) open the downloaded servlet tag containing files, (2) extract the CPIR-enabling servlet tags contained therewithin, and (3) embed (i.e. insert) one or more distributed CPIR-enabled servlets HMTL tags into acceptable HTML-encoded documents associated with EC-enabled WWW sites, EC-enabled storefronts and catalogs, Internet product advertisements, on-line auction-based WWW sites, or other types of Web-documents.

In general, this step of the method involves first creating or otherwise procuring a suitable HTML-encoded document which may, understandably include other types of code (e.g. XML) therein, other than HTML code. While such HTML documents can be created using any HTML-editing program, such as BBD-Edit, it is expected that in most applications the underlying HTML-encoded document will be generated using tools such as, for example: GO-LIVE® WWW-Site Development and Management solution software from Adobe Systems, Inc. to create the HTML pages associated with a particular WWW site; CatalogMaker™™ and CatalogManager electronic commerce solution software programs from RealEDI, Inc; Intershop 4 Enfinity™ Electronic Commerce Solution software from Intershop Communications, Inc; and/or any other commercially available HTML-authoring tools which enable quick and easy creation of HTML-encoded documents, and easy insertion of any downloaded CPIR-enabling servlet tag <SERVLET> using, for example, simple commands or drag-and-drop procedures.

As indicated at Block E in FIG. 4E2, the eighth step of the method involves serving “servlet-tag” encoded HTML documents from Internet information servers to Java-enabled client computer subsystems 13 operated by consumers at home, in the office, in EC-enabled or “brick and mortar” retail stores, or on -the road, as the case may be. As shown in FIG. 4F, such Internet information servers can include, for example, IPI servers 12, retailer-related EC-enabled information servers 12A, manufacturer-related EC-enabled information servers 12B, and/or any other Internet (http or ftp) information servers operating on the Internet from which HTML-encoded document are served for any informational, educational, and/or entertainment purpose.

As indicated at Block F in FIG. 4E2, the ninth step of the method hereof involves using a Java-enabled client computer subsystems 13 to display served HTML-encoded documents having one or more of CPIR-enabling servlet tags embedded therewithin. This step is carried out by the consumer pointing his or her Java-enabled browser program (e.g. Netscape Navigator, Microsoft Explorer, or Sun Microsystems' HotJava program) to an HMTL-encoded document within which a CPIR-enabling Java servlet tag is embedded, at a particular point of presence on the WWW. As shown in FIGS. 4M1 through 4R2, CPIR-enabling Applets can be graphically-encoded in an variety of different ways to provide the consumer with a visual indication that, clicking on the graphical object however manifested, will automatically result in a consumer product information search on a particular product identified by the UPN encoded within the associated servlet. In view of the fact the CPIR-enabling servlet tags are distributed over the Internet and inserted within HTML documents by others than the servlet author, at some future date, graphical encoding of CPIR-enabling servlets will typically occur at the time of writing the servlet.

With the above point in mind, it will be helpful to adopt a standardized icon for graphically indicating the presence of a CPIR-enabling servlet tag within an HTML document. In the illustrative embodiments shown in FIGS. 4P1, 4P2, 4R1, 4R2, 4S1, and 4S2, small predefined images of servicemarks such as “GO: UPC Request Cyber-Service™ URL Search” are served to inform the consumer that the Java object, if selected from the displayed Web page, will automatically cause a product-specific URL search to be performed with respect to the particular consumer product and the results thereof displayed at the “point of presence” of the consumer who may be residing at a particular point in an EC-enabled store (e.g. at the check-out display screen or POS), at on-line auction site, at a Web-based product advertisement, or anywhere else on the WWW. Notably, an important advantage provided by this information search technique of the present invention is that it does not disturb the consumer at his or her point of presence (or sale), where ever that may be. Instead, the CPI search and display method hereof enables the delivery of accurate product-specific manufacturer-defined information at precise points in Cyberspace by performing a single mouse-clicking operation. This enables consumers to make informed decisions thereat based on the information displayed in the corresponding Java GUI generated upon launching a CPIR-enabling servlet at the consumer's point of presence on the WWW.

It is understood, however, that other techniques may be used to create visual indication to the consumer that a CPIR-enabling Applet is located at a particular point on the WWW and that if this Applet is executed (e.g. by a single mouse-clicking operation), then a UPN-directed consumer product information search will be automatically executed and the results therefrom will be displayed within a Java GUI at the consumer's point of presence.

One alternative technique would be to embed within the CPIR-enabling Applet, a thumb-nail or large size photo-image of the consumer product being offered for sale, lease, auction, or other purpose on the WWW. Notably, this product image any reside on the RDBMS server 9, or on the http server from which the HTML-encoded document is served. Using this technique, the consumer need only click on the image to initiate a UPN-directed consumer product information search against the UPN/URL Database Management Subsystem 9 hereof.

Notably, the person or persons responsible for delivering product advertisements to particular locations on one or more WWW sites can use the OPEN ADSTREAM™ (OAS) 5.0 Internet Advertisement Management Solution software from Real Media, Inc., of New York, N.Y., and any other suitable software solution, running on the Internet (http) information server (12, 12′, 12A or 12B), and managed using an Web-enabled client subsystem 13, as shown in FIG. 4F1. Using the OAS 5.0 advertisement management solution, and the CPI search and display method of present invention described above, a webmaster or advertising manager assigned to a particular Internet information server (12, 12′, 12A or 12B) can: (1) access the Web-based product advertisement for a particular product (i.e. HTML code, image files, and any other rich media content associated therewith); (2) access previously downloaded CPIR-enabling Java servlet(s) for the consumer product, stored in a locally-maintained “Library (i.e. Catalog) of CPIR-Enabling Applets” on a client machine or server on the network, or directly access CPIR-enabling Java servlets from the centrally-maintained “Library (i.e. Catalog) of CPIR-Enabling Applets” illustrated in FIG. 4F1, via the Java Web Server 11′; and (3) use Real Media's OAS 5.0 solution software deliver both the Web-based product advertisement (i.e. its HTML code and other media-rich content) and the corresponding CPIR-enabling Applet tag (and possibly any image files associated therewith) to a designated section on a particular Web page of a specific WWW-site.

It is understood that there are different ways of inserting/embedding both of these objects within a particular section of an HTML-encoded document using the highly-advanced HTML-editing functionalities of the OAS 5.0 software system. For example, the Web-based product advertisement can be inserted within a first spatially-defined portion of the target HTML document (occupying the largest portion of the purchased Internet advertising space), while the CPIR-enabling server-side Applet (i.e. servlet) is inserted within a second spatially-defined portion of the target HTML document occupying the balance of the purchased Internet advertising space. Alternatively, both the CPIR-enabling Applet and the Web-based product advertisement can be inserted within substantially same spatially-defined portion of the target HTML document so as to achieve spatial overlap therebetween. This way when the consumer clicks on the advertisement image, or some preselected portion thereof, the underlying CPIR-enabling servlet will be automatically executed and the corresponding Java GUI generated for displaying the results of the UPN-directed database search.

In situations where the Internet product advertisement (e.g. banner advertisement) embodies a servlet HMTL tag which, when executed, produces a new Java GUI (i.e. new browser interface), then a CPIR-enabling servlet can be embedded within the HTML-encoded document displayed in the new Java GUI. This servlet tag embedding technique will be useful in many applications where the display space allocated for the Web advertisement in the target HTML-encoded document is limited, and there is a need to generate a new Java GUI for presenting the content of the advertisement.

Other ways of embedding the Web-based advertisement and the related CPIR-enabling servlet tags will become apparent hereinafter to those skilled in the art having had the benefit of reading the present disclosure.

As indicated at Block G in FIG. 4E2, the tenth step in the method involves the consumer recognizing that a CPIR-enabling servlet tag is embedded within a Web-document displayed on a Java-enabled client computer subsystem, and thereafter launching/executing the associated servlet to initiate a UPN-directed consumer product information search within the RDBMS server 9.

Notably, the above illustrative embodiment has been described with particular focus given to CPIR-enabling servlets encoded with the UPN of a particular consumer product. It is understood, however, that the CPIR-enabling servlets of the present invention can be encoded with the trademark(s) used in connection with a particular consumer product, thus providing Trademark-encoded CPIR-enabling servlets, in contrast with UPN-encoded CPIR-enabling servlets. In such alternative embodiments, the encoded trademark would be used to direct a search through the RDBMS server 9, and display the results thereof in a new (independent) Java GUI generated at the point of servlet tag embodiment. Alternatively, a product descriptor associated with a particular product can be encoded within the corresponding CPIR-enabling servlet, used to direct a search through the RDBMS server 9, and display the results thereof in an independent Java GUI generated at the point of servlet tag embodiment.

The Second Applet-Driven Method of Accessing and Displaying Categorized UPN/URL Link Menus from the UPN/URL Database Management Subsystem the Present Invention

After providing a brief overview on the system architecture of FIG. 2B2 and the nature of the client-side CPIR-enabling Applets deployed therewithin, the steps associated with Applet-driven CPI-acquisition method of the second illustrative embodiment will be described in detail with reference to FIGS. 4GI, 4G2, 4H1 and 4H2.

In general, the method of FIGS. 4G1 and 4G2 involves using a client-side CPIR-enabling Applet to automatically conduct a UPN-directed search on the UPN/URL Database Management Subsystem hereof (i.e. RDBMS server 9) in response to a single mouse-clicking operation by the consumer on the HTML tag associated with the CPIR-enabling Applet. In the illustrative embodiment, the CPIR-enabling Applet of the present invention is a program written in the Java™ programming language and has an HTML tag (indicated by <APPLET>) which is designed to be included in an HTML page, much in the same way an image can be included therewithin (according to the HTML 3.2 Specification).

CPIR-enabling Applets of the present invention are designed to work within a request/response processing model, as shown in FIG. 2B2. In this request/response model, a client subsystem 13 sends a request message to the Java Web Server 11″ and the Server 11″ responds by sending back a reply message. In the illustrative embodiment, requests come in the form of http, although is understood that the use of other protocol as such as ftp, EDI or a custom protocol, may be possible in particular embodiments. The request and the corresponding response reflect the state of the client and the server at the time of the request.

When using a Java-enabled browser to view a Web page containing a client-side CPIR-enabling Applet tag <APPLET>, the Applet's compiled class code is automatically accessed from the Java Web Server 11″ and executed on the client-side of the network connection illustrated in FIG. 2B2. Thus, as shown in FIG. 2B2, the Java-enabled client machine 13 in this network architecture must run a Java-enabled browser program that provides a Java Virtual Machine (JVM) for running/executing Java Applets on the client-side of the network in much the same way that Java Web Server 11″ must provide a JVM for running Java servlets on the server side thereof, as shown in FIG. 2B1.

As shown in FIG. 2B2, the Java-enabled Web browser 13 includes a number of software components including Java interfaces for fully defining the link between the Java Web browser and the Applets located at the middle tier. In order to write, compile and load Applets onto the Java Web Server 11″, the system administrator or webmaster can use the Java API provided for within the Java 2 (development) platform from JavaSoft, a division of Sun Microsystems, Inc. This platform also supports The API specification of the Java 2 Platform, Standard Edition, version 1.2.2, comprises the following Packages:

-   (1) java.applet: Provides the classes necessary to create an applet     and the classes an applet uses to communicate with its applet     context. -   (2) java.awt: Contains all of the classes for creating user     interfaces and for painting graphics and images. -   (3) java.awt.color: Provides classes for color spaces. -   (4) java.awt.datatransfer: Provides interfaces and classes for     transferring data between and within applications. -   (5) java.awt.dnd: Drag and Drop is a direct manipulation gesture     found in many Graphical User Interface systems that provides a     mechanism to information between two entities logically associated     with presentation elements in the GUI. -   (6) java.awt.event: Provides interfaces and classes for dealing with     different types of events fired by AWT components. -   (7) java.awt.font: Provides classes and interface relating to fonts. -   (8) java awt.geom: Provides the Java 2D classes for defining and     performing operations on objects related to two-dimensional     geometry. -   (9) java.awt.im: Provides classes and an interface for the input     method framework. -   (10) java.awt.image: Provides classes for creating and modifying     images. -   (11) java awt.image.renderable: Provides classes and interfaces for     producing rendering-independent images. -   (12) java.awt.print: Provides classes and interfaces for a general     printing API. -   (13) java.beans: Contains classes related to Java Beans development. -   (14) java.beans.beancontext: Provides classes and interfaces     relating to bean context. -   (15) java.io: Provides for system input and output through data     streams, serialization and the file system. -   (16) java lang: Provides classes that are fundamental to the design     of the Java programming language. -   (17) java.lang.ref: Provides reference-object classes, which support     a limited degree of interaction with the garbage collector. -   (18) java.lang.reflect: Provides classes and interfaces for     obtaining reflective information about classes and objects. -   (19) java.math: Provides classes for performing arbitrary-precision     integer arithmetic (BigInteger) and arbitrary-precision decimal     arithmetic (BigDecimal). -   (20) java.net: Provides the classes for implementing networking     applications. -   (21) java.rmi: Provides the RMI package. -   (22) java.rmi.activation: Provides support for RMI Object     Activation. -   (23) java.rmi.dgc: Provides classes and interface for RMI     distributed garbage-collection (DGC). -   (24) java.rmi.registry: Provides a class and two interfaces for the     RMI registry. -   (25) java.rmi.server: Provides classes and interfaces for supporting     the server side of RMI. -   (26) java.security: Provides the classes and interfaces for the     security framework. -   (27) java.security.cert: The classes and interfaces in this package     have been superseded by classes in the java.security package. -   (28) java.security.cert: Provides classes and interfaces for parsing     and managing certificates. -   (29) java.security.interfaces: Provides interfaces for generating     RSA (Rivest, Shamir and Adleman AsymmetricCipher algorithm) keys as     defined in the RSA Laboratory Technical Note PKCS#1, and DSA     (Digital Signature Algorithm) keys as defined in NIST's FIPS-186. -   (30) java.security.spec: Provides classes and interfaces for key     specifications and algorithm parameter specifications. -   (31) java.sql: Provides the JDBC package. -   (32) java.text: Provides classes and interfaces for handling text,     dates, numbers and messages in a manner independent of natural     languages. -   (33) java.util: Contains the collections framework, legacy     collection classes,event model, date and time facilities,     internationalization, and miscellaneous utility classes (a string     tokenizer, a random-number generator, and a bit array). -   (34) java.util.jar: Provides classes for reading and writing the JAR     (Java ARchive) file format, which is based on the standard ZIP file     format with an optional manifest file. -   (35) java.util.zip: Provides classes for reading and writing the     standard ZIP and GZIP file formats. -   (36) javax.accessibility: Defines a contract between user-interface     components and an assistive technology that provides access to those     components. -   (37) javax.swing: Provides a set of “lightweight” (all-Java     language) components that, to the maximum degree possible, work the     same on all platforms. -   (38) javax.swing border: Provides classes and interface for drawing     specialized borders around a Swing component. -   (39) javax.swing.colorchooser: Contains classes and interfaces used     by the JcolorChooser component. -   (40) javax.swingevent: Provides for events fired by Swing     components. -   (41) javax swing.filechooser: Contains classes and interfaces used     by the JfileChooser component. -   (42) javax.swing.plaf: Provides one interface and many abstract     classes that Swing uses to provide its pluggable look-and-feel     capabilities. -   (43) javax.swing.plaf.basic: Provides user interface objects built     according to the Basic look-and-feel. -   (44) javax.swing.plaf.metal: Provides user interface objects built     according to the metal” look-and-feel. -   (45) javax.swing.plaf.multi: The multiplexing look and feel allows     users to combine auxiliary look and feels with the default look and     feel. -   (46) javax.swing.table: Provides classes and interfaces for dealing     with java.awt.swing.JTable. -   (47) javax.swing.text: Provides classes and interfaces that deal     with editable and noneditable text components. -   (48) javax.swing.text.html: Provides the class HTMLEditorKit and     supporting classes for creating HTML text editors. -   (49) javax.swing.text.html.parser -   (50) javax.swing.text.rtf: Provides a class (RTFEditorKit) for     creating Rich-Text-Format text editors. -   (51) javax.swing.tree: Provides classes and interfaces for dealing     with java.awt.swing.JTree. -   (52) javax.swing.undo: Provides support for undo/redo capabilities     in an application such as a text editor. -   (53) org.omg.CORBA: Provides the mapping of the OMG CORBA APIs to     the Java™ programming language, including the class ORB, which is     implemented so that a programmer can use it as a fully-functional     Object Request Broker (ORB). -   (54) org.omg.CORBA.DynAnyPackage: Provides the exceptions used with     the DynAny interface (InvalidValue, Invalid, InvalidSeq, and     TypeMismatch). -   (55) org.omg.CORBA.ORBPackage: Provides the exception InvalidName,     which is thrown by the InconsistentTypeCode, which is thrown by the     Dynamic Any creation methods in the ORB class. -   (56) org.omg.CORBA.portable: Provides a portability layer, that is,     a set of ORB APIs that makes it possible for code generated by one     vendor to run on another vendor's ORB. -   (57) org.omg.CORBA.TypeCodePackage: Provides the user-defined     exceptions BadKind and Bounds, which are thrown by methods in the     class TypeCode. -   (58) org.omg CosNaming: Provides the naming service for Java IDL. -   (59) org.omg.CosNaming.NamingContextPackage: Provides the exceptions     used in the package org.omg.CosNaming (AlreadyBound, CannotProceed,     InvalidName, NotEmpty, and NotFound) and also the Helper and Holder     classes for those exceptions.

Having provided an overview on client-side CPIR-enabling Java Applets of the present invention and the support framework required thereby in a distributed-computing object oriented programming environment shown in FIG. 2B2, it is appropriate to now describe, the method of creating, loading, distributing, embedding and executing client-side CPIR-enabling Java Applets in accordance with the principles of the present invention schematically illustrated in FIGS. 4G1, 4G2, 4HI and 4H2.

As indicated at Block A1 in FIG. 4G1, the first step of the method involves using the Java Applet API to write or otherwise author the source code for a client-side CPIR-enabling Java Applet for each UPN-specified consumer product registered in the RDBMS server 9. In general, the source code for each client-side CPIR-enabling Java Applet (i.e. Applet) will embody one or more of following items of information: (i) the UPN of the particular product on which the CPI-based search is to be carried out and the search results thereof displayed; (ii) Java classes required for performing a UPN-directed search on the RDBMS server 9 using a CGI script executing on the Java Web Server 11″, and producing a particular Java GUI for displaying the results obtained from the UPN-directed search; and (iii) license-related information specifying the terms and conditions of the CPIR-enabling Applet license and conditions under which the CPIR-enabling Applet shall operate.

Notably, such license-related information may specify: (1) one or more specific host domains (e.g. www.homedepot.com or www.walmartcom) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (2) one or more general Internet domains (e.g. .com, .org., .gov, .int, .mil, .uk, etc.) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (3) the time duration of the licensing period associated with the CPIR-enabling Applet; and (4) any other restrictions set by the associated manufacturer and/or retailer, and/or administrator of the consumer product information system of the present invention, that must be satisfied for a registered CPIR-enabled Applet to operate within a Web-document.

Notably, the Java source code for each CPIR-enabling Applet will vary depending upon implementation. However, regardless of the particular implementation, it can be expected that each CPIR-enabling Applet designed, for example, to search an (Oracle-based JDBC) RDBMS Server 9 for a current catagorized UPC/URL list/menu symbolically linked to a specified UPN and thereafter display the results in an independent Java GUI, will typically include Java source code specifying:

-   (1) the importable JDBC classes required by the CPIR-enabling     Applet; -   (2) the importable java classes to be used in the CPIR-enabling     Applet; -   (3) the JDBC driver to be loaded for the Oracle-based RDBMS server     9; -   (4) the connection strings to the RDBMS server 9; -   (5) the CPI query to be executed on the UPN/URL Database, dependent     on the UPN of the associated consumer product and possibly other     search criteria and Applet licensing conditions; -   (6) the Applet tag, its graphical icon or alias to trigger execution     the Applet and its associated CPI query; -   (7) the CPI Search Result GUI to be displayed on requesting client     and its relative location to the associated applet tag; and -   (8) the operations that will be carried out upon execution of the     CPI query including     -   Boolean search logic to be carried out upon initiation of the         UPN-directed CPI search;     -   if a new connection is required between Java Web Server 11″ and         the RDBMS server 9;     -   Loading the JDBC driver;     -   Connecting to the RDBMS server 9;     -   Creating a SQL statement based on the specified Boolean search         logic and UPN;     -   Executing the SQL query statement; and         -   Dumping the search results to the CPI Search Result GUI.

When using earlier versions of the HTML Specification (i.e. HTML 3.2 by the World Wide Web Consortium), the source code for each CPIR-enabling Java Applet would adhere to the following general syntax:

[CODEBASE = codebaseURL] CODE — appletFile [ALT = alternateText] [NAME = appletInstanceName] WIDTH = pixels HEIGHT = pixels [ALIGN = alignment] [VSPACE = pixels] [HSPACE = pixels] > [<PARAM NAME = Attribute1 VALUE = value >] [<PARAM NAME = Attribute2 VALUE = value >] . . . [alternateHTML] </APPLET> wherein the set of brackets [ ] indicates optional parameters within the HTML 3.2 Specification.

The optional <PARAM> tag lets you to specify applet-specific attributes that your applet can retrieve as Strings. These Strings can be used in an HTML document to customize the Applet's behavior and supply their respective values in command-line variables.

CODEBASE, CODE, WIDTH, and HEIGHT are attributes specified by the first part of the <APPLET> tag. The Java-enabled Web browser 13 uses these attributes to locate the CPIR-enabling Applet code on the Java Web Server 11″ and to indicate the amount of space to be reserved in the target HTML document during display. CODEBASE directs the Java-enabled Web browser to look for code in the classes directory of the Java Web Server 11″. The mandatory parameter CODE provides the name of the Java code file that is to be loaded from the Java Web Server 11″. Any other class files used by the Applet are loaded from the Codebase Directory as well.

WIDTH and HEIGHT are attributes that tell the Java-enabled Web browser to reserve space in the document display before the Java code is loaded (“x” pixels wide by “x” pixels high), similar to the way browsers deal with images, reserving space before the complete image is available. To place an invisible Applet on a page, specify height and width of zero.

Current Java-enabled Web browsers ignore the Java language resize( ) method for applets. Although the applet viewer provided in the JDK responds to the resize( ) method, one will have to specify width and height correctly in the CPIR-enabling APPLET tag for general Web browsers.

VSPACE and HSPACE are attributes for specifying the amount of space (in pixels) that surrounds the CPIR-enabling Applet above and below (vspace) and on each side (hspace) of the Applet area.

ALIGN is another attribute used to designate where the Java-enabled Web browser is to place the Applet area in relation to any other design elements. ALIGN can have possible values like those for the IMG tag: left, right, top, texttop, middle, absmiddle, baseline, bottom, and absbottom.

Notably, the optional parameters ALIGN, VSPACE and HSPACE may be set either at the time of CPIR-enabling Applet creation (i.e. when writing the source code therefor), or at the latter time such as, for example, after compiling and loading the Java class code on the Java Web Server, after downloading CPIR-enabling Applet tag files, or after extracting CPIR-enabling Applets, but prior to embedding the CPIR-enabling Applet tag within a HTML-encoded document. Thus, these optional parameters enable the Web page, EC-commerce site and auction site designer to modify (after Java class code compiling and loading operations, but before Applet tag insertion/embedding operations) certain parameters and attributes within each CPIR-enabling Applet tag that determine the precise location where the Java-enabled browser on the client machine 13 will display the CPIR-enabling Applet and its associated image graphics on the browser display screen.

The ALT attribute designates a string to be displayed if the browser understands the <APPLET> tag but does not have Java capabilities. Netscape 2.0 allows turning the Java interpreter on or off via a check box under Options on the Security Preferences menu. The ALT attribute is a way to remind users to turn Java back on after turning it off to avoid wasting time on slow applets (as can often occur on Web pages).

CPIR-enabling Applets that coexist on the same Web page communicate by means of the NAME attribute. The AppletContext method getApplet(String name) returns a reference to the named Applet if it can be found in the Web page and then allows communication between Applets in the conventional sense.

The PARAM tag is used in transferring text information to the Applet code by way of the getParameter(String param_name) applet method. Since the parameter-matching code is not case sensitive and quote marks are parsed out, the following tags are equivalent:

-   <PARAM name=EMAIL -   <param NAME=EMAIL -   <param name=“email”     Between the last <PARAM> tag and the </APPLET> tag, text and HTML     code can be designated for display if the Web browser of a     particular client system cannot recognize the <APPLET> tag. Notably,     the content of the Applet tag acts as alternate information for     client subsystems that do not support this element or are currently     configured not to support Applets. Otherwise, the content of the     Applet must be ignored.

The final element of the Applet tag must be </applet> in order to tell the Web browser that the Applet has ended.

Notably, in the HTML 4.0 Specification, published by the World Wide Web Consortium at http://www.w3.org/TR/WD-html40-970917/, the Applet element has been deprecated in favor of the OBJECT element, which offers an all purpose solution to generic object inclusion. The HTML 4.0 Specification now allows the OBJECT element to include images (via the <IMG> tag) and Applets (via the <APPLET> tag) in the same manner. Thus, when constructing Web documents and CPIR-enabling Applets in accordance with the HTML 4.0 Specification, the source code for each CPIR-enabling Applet will adhere to an entirely different syntax, the details of which are set forth which in the HTML 4.0 Specification, supra, are incorporated herein by reference.

For additional details pertaining to Java Applet construction, embedding techniques and Java GUI design and development, reference can be made to the following technical publications: “JAVA” (1997) by Ed Tittel and Bill Brogden, published by IDG Books Worldwide, Inc.; “Wilde's WWW: Technical Foundations of the World Wide Web” (1999) by Erik Wilde, published by Springer-Verlag, Berlin, Heidelberg; “The Java™ Tutorial Second Edition: Object Oriented Programming For The Internet” (1999), by Mary Campione and Kathy Walrath, published by Sun Microsystems, Inc., of Palo Alto, Calif.; and “The JFC Swing Tutorial: A Java Guide To Constructing JAVA GUIs” (1999), by Mary Campione and Kathy Walrath, published by Sun Microsystems, Inc., of Palo Alto, Calif.; each said publication being incorporated herein by reference.

After writing/authoring the source code for the Applet, the CPIR-enabling Java Applet is ascribed a unique name such as, for example, “UPNXXXXXXYYYYYZ” for a 12 digit Uniform Product Code.

As indicated at Block A2 in FIG. 4G1, the second step of the method involves compiling the source code of the Applet into Java bytecode, and then placing/loading the classfiles for the Applet within the server_root/Applets directory on the Java Web Server 11″.

As indicated at Block B1 in FIG. 4G1, the third step of the method involves for each UPN-specified consumer product, (1) containing the complete Applet HMTL tag <APPLET> within an executable file, and (2) storing each such Applet tag containing file in the Central CPIR-Enabling Applet Library on the RDBMS server 9, as shown in FIG. 4H1.

As indicated at Block C in FIG. 4G1, the fourth step of the method involves distributing the CPIR-enabling Applet HMTL tags to retailers, wholesalers, advertisers, and others who desire to deliver UPN-directed CPI search results to their customers, clients and the like. This distribution process may be carried out in a number of ways.

For example, in one embodiment of the present invention shown in FIG. 4M1, retailers, wholesalers, advertisers, and others would visit the IPI Central WWW site as shown in FIG. 3C and selected the Applet Tag Download/Distribute Mode by selecting mode control button 21F, whereupon a (Java) GUI, is displayed in the display frame 20C. Within this GUI, a “master” list of executable files containing CPIR-enabling Applet tags is displayed for each consumer product registered within the system. The CPIR-enabling Applet tag containing file associated with any particular consumer product can be searched for by UPN, trademark, and/or product descriptor, and once found, can be viewed and simply downloaded to a remote client computer system connected to the Internet using, for example, ftp or other electronic data or document interchange protocols (e.g. XML/ICE) suitable for carrying out the <APPLET> tag transport process. Downloaded CPIR-enabling Applet tag containing files can be then stored in a local CPIR-enabling Applet/Servlet Library maintained on a client computer until it is time to extract the Applet tag therefrom and embed the same into a particular HTML-encoded document.

In an alternative embodiment shown in FIG. 4M2, the distribution of CPIR-enabling Applet tags is enabled by providing a “CPIR-enabling Applet Tag Download” Link/Button 100 on the Web page of each product being offered for sale in an EC-enabled store or product catalog maintained by a manufacturer, retailer or other party. This inventive feature should be most useful in EC-enabled Business-to-Business (i.e. Vendor-to-Retailer) UPC-based Product Catalogs such as, for example, QRS's Keystone UPC Product Catalog, where purchasing agents of retailers could download “Applet tag containing” files, along with product images and other product information after placing a purchase order therethrough, for use in constructing the retailer's EC-enabled (retailer-to-consumer) store or product catalog. Using this method of the present invention, consumers would be provided with instant manufacturer-defined product information prior to, and/or after a consumer purchase at an EC-enable store on the WWW, thereby greatly improving the consumer shopping experience on the WWW.

As indicated at Block D in FIG. 4G2, the fifth step of the method involves enabling retailers, wholesalers, advertisers, and others to (1) open the downloaded Applet tag containing files, (2) extract the CPIR-enabling HMTL tags contained therewithin, and (3) embed (i.e. insert) one or more distributed CPIR-enabled Applet tags into acceptable HTML-encoded documents associated with EC-enabled WWW sites, EC-enabled storefronts and catalogs, Internet product advertisements, on-line auction-based WWW sites, or other types of Web-documents.

In general, this step of the method involves first creating or otherwise procuring a suitable HTML-encoded document which may understandably include other types of code (e.g. XML) therein, other than HTML code. While such HTML documents can be created using any HTML-editing program, such as BBD-Edit, it is expected that in most applications the underlying HTML-encoded document will be generated using tools such as, for example: GO-LIVE® WWW-Site Development and Management solution software from Adobe Systems, Inc. to create the HTML pages associated with a particular WWW site; CatalogMaker™™ and CatalogManager electronic commerce solution software programs from RealEDI, Inc; Intershop 4 Enfinity™ Electronic Commerce Solution software from Intershop Communications, Inc; and/or any other commercially available HTML-authoring tools which enable quick and easy creation of HTML-encoded documents, and easy insertion of any downloaded CPIR-enabling Applet HMTL tag using, for example, simple commands or drag-and-drop procedures.

As indicated at Block E in FIG. 4G2, the sixth step of the method involves serving HTML documents with inserted CPIR-enabling Applet tags, from Internet information servers to Java-enabled client computer subsystems 13 operated by consumers at home, in the office, in EC-enabled and “brick and mortar” retail stores, or on the road, as the case may be. As shown in FIG. 4H1, such Internet information servers can include, for example, IPI servers 12, retailer-related EC-enabled information servers 12A, manufacturer-related EC-enabled information servers 12B, and/or any other Internet (http or ftp) information servers operating on the Internet from which HTML-encoded document are served for any informational, educational, and/or entertainment purpose.

As indicated at Block F in FIG. 4G2, the seventh step of the method hereof involves using a Java-enabled client computer subsystem 13 to display served HTML-encoded documents having one or more of CPIR-enabling Applet tags embedded therewithin. This step is carried out by the consumer pointing his or her Java-enabled browser program (e.g. Netscape Navigator, Microsoft Explorer, or Sun Microsystems' HotJava program) to an HMTL-encoded document within which a CPIR-enabling Java Applet tag is embedded, at a particular point of presence on the WWW.

As shown in FIGS. 4M1 through 4R2, CPIR-enabling Applets can be graphically-encoded in an variety of different ways to provide the consumer with a visual indication that, clicking on the graphical object, however manifested, will automatically result in a CPI search on a particular product identified by a UPN encoded within the associated Applet.

In the illustrative embodiments shown in FIGS. 4P1, 4Q1, 4R1 and 4S1, servicemarks such as “UPC Request™ Cyberservice™ URL Search” serve to inform the consumer that the object, if selected from the displayed Web page, will cause a URL search to be performed with respect to the particular consumer product and the results thereof displayed the “point of presence” of the consumer which may be at a particular point in an EC-enabled store (e.g. at the check-out display screen or POS), at on-line auction site, at a Web-based product advertisement, or anywhere else on the WWW. Notably, an important advantage provided by this information search technique of the present invention is that it does not disturb the consumer at his or her point of presence (or sale), where ever that may be. Instead, the CPI-based search and display method of the present invention enables the delivery of accurate product-specific manufacturer-defined information at a particular point in Cyberspace by the consumer performing a single mouse-clicking operation. This enables the consumer to make an informed decision thereat based on the information displayed in the corresponding Java GUI generated upon launching the CPIR-enabling Applet at the consumer's point of presence on the WWW.

It is understood, however, that other techniques may be used to create a visual indication to the consumer that a CPIR-enabling Applet is located at a particular point on the WWW and that if this Applet is executed (e.g. by a single mouse-clicking operation), then a UPN-directed consumer product. information search will be automatically executed and the results therefrom will be displayed within a Java GUI at that point of presence. One alternative technique would be to embed the CPIR-enabling Applet within a thumb-nail or large size photo-image of the consumer product being offered for sale, lease, auction, or other purpose on the WWW. Using this technique, the consumer need only click on the image to initiate a UPN-directed consumer product information search on the IPI Registrant Database (e.g. RDBMS Server 9) of the system.

Notably, the person or persons responsible for delivering product advertisements to particular locations on one or more WWW sites can use the OPEN ADSTREAM™ (OAS) 5.0 Internet Advertisement Management Solution software from Real Media, Inc., of New York, N.Y., and any other suitable software solution, running on the Internet (http) information server (12, 12′, 12A or 12B), and managed using an Web-enabled client subsystem 13, as shown in FIG. 4H2. Using the OAS 5.0 advertisement management solution, and the CPI search and display method of the present invention described above, a webmaster or advertising manager assigned to a particular Internet information server (12, 12′, 12A or 12B) can: (1) access the Web-based product advertisement for a particular product (i.e. HTML code, image files, and any other rich media content associated therewith); (2) access previously downloaded CPIR-enabling Java Applet(s) for the consumer product, stored in a locally-maintained “Library (i.e. Catalog) of CPIR-Enabling Applets” on a client machine or server on the network, or directly access CPIR-enabling Java Applets from the centrally-maintained “Library (i.e. Catalog) of CPIR-Enabling Applets” illustrated in FIG. 4H2; and (3) use Real Media's OAS 5.0 solution software to deliver both the Web-based product advertisement (i.e. its HTML code, and other media-rich content) and the corresponding CPIR-enabling Applet tag (and image files associated therewith) to a designated section on a particular Web page of a specific WWW-site.

It is understood that there are different ways of inserting/embedding both of these objects within a particular section of an HTML-encoded document using the highly-advanced HTML-editing functionalities of the OAS 5.0 software system. For example, the Web-based product advertisement can be inserted within a first spatially-defined. portion of the target HTML document (occupying the largest portion of the purchased Internet advertising space), while the CPIR-enabling client-side Applet is inserted within a second spatially-defined portion of the target HTML document occupying the balance of the purchased Internet advertising space. Alternatively, both the CPIR-enabling Applet and the Web-based product advertisement can be inserted within substantially same spatially-defined portion of the target HTML document so as to achieve spatial overlap therebetween. This way when the consumer clicks on the advertisement image, or some preselected portion thereof, the underlying CPIR-enabling Applet will be automatically executed and the corresponding Java GUI generated for displaying the results of the UPN-directed database search.

In situations where the Internet product advertisement (e.g. banner advertisement) embodies a Java Applet tag which, when executed, produces a new Java GUI (i.e. new browser interface), then a CPIR-enabling Applet tag can be embedded within the HTML-encoded document displayed in the new Java GUI.

Other ways of embedding the Web-based advertisement and the related CPIR-enabling Applet tags will become apparent hereinafter to those skilled in the art having had the benefit of reading the present disclosure.

As indicated at Block G in FIG. 4G2, the eight step in the method involves the consumer recognizing that a CPIR-enabling Applet tag is embedded within a Web-document displayed on a Java-enabled client computer subsystem 13, and thereafter launching/executing the associated Applet to initiate a UPN-directed search within the RDBMS server 9 by performing a single mouse clicking operation.

Notably, the second illustrative embodiment described above has been described with particular focus given to CPIR-enabling Applets encoded with the UPN of a particular consumer product. It is understood, however, that the CPIR-enabling Applets of the present invention can be encoded with the trademark(s) used in connection with a particular consumer product, thus providing Trademark-encoded CPIR-enabling Applets, in contrast with UPN-encoded CPIR-enabling Applets. In such alternative embodiments, the encoded trademark would be used to direct a search through the RDBMS server 9, and display the results thereof in a new (independent) Java GUI generated at the point of Applet tag embodiment. Alternatively, a product descriptor associated with a particular product can be encoded within the corresponding CPIR-enabling Applet, used to direct a search through the RDBMS server 9, and display the results thereof in an independent Java GUI generated at the point of Applet tag embodiment.

The Third Applet-Driven Method of Accessing and Displaying Categorized UPN/URL Link Menus from the UPN/URL Database Management Subsystem the Present Invention

After providing a brief overview on the system architecture of FIG. 2B3 and the nature of the client-side CPIR-enabling Applets deployed therewithin, the steps associated with Applet-driven CPI-acquisition method of the third illustrative embodiment will be described in detail with reference to FIGS. 4I1, 4I2, 4J1 and 4J2.

In general, the method of FIGS. 4I1 and 4I2, like that of FIGS. 4G1 and 44G2, involves using a client-side CPIR-enabling Applet to automatically conduct a UPN-directed search on the UPN/URL Database Management Subsystem hereof (i.e. RDBMS server 9) in response to a single mouse-clicking operation by the consumer on the HTML tag associated with the CPIR-enabling Applet. In the illustrative embodiment, the CPIR-enabling Applet of the resent invention is a program written in the Java™ programming language and has an HTML tag (indicated by <APPLET>) which is designed to be included in an HTML page, much in the same way an image can be included therewithin (in accordance with the HTML 3.2 Specification).

In the method of the second illustrative embodiment, CPIR-enabling Applets are designed to work within a request/response processing model, as shown in FIG. 2B3. In this request/response model, a client subsystem 13 sends a request message to the Java Web Server 11′″ and the server 11′″ responds by sending back a reply message. In the illustrative embodiment, requests come in the form of http, although it is understood that other protocols (e.g. ftp, EDI or a custom protocol) may be used. The request and the corresponding response reflect the state of the client and the server at the time of the request.

When using a Java-enabled browser to view a Web page containing a client-side CPIR-enabling Applet tag <APPLET>, the Applet's compiled class code is automatically accessed from the Java Web Server 11′″. and executed on the client-side of the network connection illustrated in FIG. 2B3. Thus, as shown in FIG. 2B3, the Java-enabled client machine 13 in this network architecture must run a Java-enabled browser program that provides a Java Virtual Machine (JVM) for running/executing Java Applets on the client-side thereof, in much the same way that Java Web Server 11′ must provide a JVM for running Java servlets on the server side thereof, as shown in FIG. 2B1.

With reference to FIG. 2B3, the method of creating, loading, distributing, embedding and executing client-side CPIR-enabling Java Applets in accordance with the principles of the present invention schematically illustrated in FIGS. 4I1, 4I2, 4J1 and 4J2 will now be described below.

As indicated at Block A1 in FIG. 4I1, the first step of the method involves using the Java Applet API to write or otherwise author the source code for a client-side CPIR-enabling Java Applet for each UPN-specified consumer product registered in the RDBMS server 9. In general, the source code for each client-side CPIR-enabling Java Applet (i.e. Applet) will embody one or more of following items of information: (i) the UPN of the particular product on which the CPI search is to be carried out and the search results thereof displayed; (ii) Java classes required for performing a UPN-directed search on the RDBMS server 9 using a “socket connection” between the Java-enabled client subsystem 13 and the Java Web Server 11′″, producing a particular Java GUI for displaying the results obtained from the UPN-directed search; and (iii) license-related information specifying the terms and conditions of the CPIR-enabling Applet license and conditions under which the CPIR-enabling Applet shall operate.

Notably, such license-related information may specify: (1) one or more specific host domains (e.g. www.homedepot.com or www.walmart.com) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (2) one or more general Internet domains (e.g. .com, .org., .gov, .int, .mil, uk, etc.) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (3) the time duration of the licensing period associated with the CPIR-enabling Applet; and (4) any other restrictions set by the associated manufacturer and/or retailer, and/or administrator of the consumer product information system of the present invention, that must be satisfied for a registered CPIR-enabled Applet to operate within a Web-document.

Notably, the Java source code for each CPIR-enabling Applet will vary depending upon implementation. However, regardless of the particular implementation, it can be expected that each CPIR-enabling Applet designed, for example, to search an (Oracle-based JDBC) RDBMS Server 9 for current UPC/URL list symbolically linked to a specified UPN and thereafter display the results in an independent Java GUI, will typically include Java source code specifying:

-   (1) the importable JDBC classes required by the CPIR-enabling     Applet; -   (2) the importable java classes to be used in the CPIR-enabling     Applet; -   (3) the JDBC driver to be loaded for the Oracle-based RDBMS server     9; -   (4) the connection strings to the RDBMS server 9; -   (5) the CPI query to be executed on the UPN/URL Database, dependent     on the UPN of the associated consumer product and possibly other     search criteria and Applet licensing conditions; -   (6) the Applet tag, its graphical icon or alias to trigger execution     the Applet and its associated CPI query; -   (7) the CPI Search Result GUI to be displayed on requesting client     and its relative location to the associated Applet tag; and -   (8) the operations that will be carried out upon execution of the     CPI query including     -   Boolean search logic to be carried out upon initiation of the         UPN-directed CPI search;     -   if a new connection is required between Java Web Server 11′″ and         the RDBMS server 9;     -   Loading the JDBC driver;     -   Connecting to the RDBMS server 9;     -   Creating a SQL statement based on the specified Boolean search         logic and UPN;     -   Executing the SQL query statement; and         -   Dumping the search results to the CPI Search Result GUI.

When using earlier versions of the HTML Specification (i.e. HTML 3.2 by the World Wide Web Consortium), the source code for each CPIR-enabling Java Applet will adhere to the general syntax of that the HTML 3.2 Specification. Also, if the HTML 4.0 Specification is used, then the source code for each CPIR-enabling Java Applet will adhere to the general syntax of the HTML 4.0 Specification, as discussed above.

After writing/authoring the source code for the CPIR-enabling Java Applet, the Applet is ascribed a unique name such as, for example, “UPNXXXXXXYYYYYZ” for a 12 digit Uniform Product Code.

As indicated at Block A2 in FIG. 4I1, the second step of the method involves compiling the source code of the Applet into Java bytecode, and then placing/loading the classfiles for the Applet within the server_root/Applets directory on the Java Web Server 11′″.

As indicated at Block B1 in FIG. 4I1, the third step of the method involves for each UPN-specified consumer product, (1) containing the complete Applet HMTL tag <APPLET> within an executable file, and (2) storing each such Applet tag containing file in the Central CPIR-Enabling Applet Library on the RDBMS server 9, as shown in FIG. 4J1.

As indicated at Block C in FIG. 4I1, the fourth step of the method involves distributing the CPIR-enabling Applet HMTL tags to retailers, wholesalers, advertisers, and others who desire to deliver UPN-directed CPI search results to their customers, clients and the like. This distribution process may be carried out in several different ways which have been detailed hereinabove in connection with the second illustrative method illustrated in FIGS. 4G1 through 4H2 and described above.

As indicated at Block D in FIG. 4G2, the fifth step of the method involves enabling retailers, wholesalers, advertisers, and others to (1) open the downloaded Applet tag containing files, (2) extract the CPIR-enabling HMTL tags contained therewithin, and (3) embed (i.e. insert) one or more distributed CPIR-enabled Applet tags into acceptable HTML-encoded documents associated with EC-enabled WWW sites, EC-enabled storefronts and catalogs, Internet product advertisements, on-line auction-based WWW sites, or other types of Web-documents.

In general, this step of the method involves first creating or otherwise procuring a suitable HTML-encoded document which may understandably include other types of code (e.g. XML) therein, other than HTML code. While such HTML documents can be created using any HTML-editing program, such as BBD-Edit, it is expected that in most applications the underlying HTML-encoded document will be generated using tools such as, for example: GO-LIVE® WWW-Site Development and Management solution software from Adobe Systems, Inc. to create the HTML pages associated with a particular WWW site; CatalogMaker™™ and CatalogManager electronic commerce solution software programs from RealEDI, Inc; Intershop 4 Enfinity™ Electronic Commerce Solution software from Intershop Communications, Inc; and/or any other commercially available HTML-authoring tools which enable quick and easy creation of HTML-encoded documents, and easy insertion of any downloaded CPIR-enabling Applet HMTL tag using, for example, simple commands or drag-and-drop procedures.

As indicated at Block E in FIG. 4G2, the sixth step of the method involves serving servlet tag encoded HTML documents from Internet information servers to Java-enabled client computer subsystems 13 operated by consumers at home, in the office, in EC-enabled and “brick and mortar” retail stores, or on the road, as the case may be. As shown in FIG. 4H1, such Internet information servers can include, for example, IPI servers 12, retailer-related EC-enabled information servers 12A, manufacturer-related EC-enabled information servers 12B, and/or any other Internet (http or ftp) information servers operating on the Internet from which HTML-encoded document are served for any informational, educational, and/or entertainment purpose.

As indicated at Block F in FIG. 4G2, the seventh step of the method hereof involves using a Java-enabled client computer subsystem 13 to display served HTML-encoded documents having one or more of CPIR-enabling Applet tags embedded therewithin. This step is carried out by the consumer pointing his or her Java-enabled browser program (e.g. Netscape Navigator, Microsoft Explorer, or Sun Microsystems' HotJava program) to an HMTL-encoded document within which a CPIR-enabling Java Applet tag is embedded, at a particular point of presence on the WWW. As shown in FIGS. 4M1 through 4R2, CPIR-enabling Applets can be graphically-encoded in an variety of different ways as described in detail detailed hereinabove in connection with the second illustrative method illustrated in FIGS. 4G1 through 4H2 and described above.

As indicated at Block G in FIG. 4G2, the eight step in the method involves the consumer recognizing that a CPIR-enabling Applet tag is embedded within a Web-document displayed on a Java-enabled client computer subsystem, and thereafter launching/executing the associated Applet to initiate a UPN-directed search within the RDBMS server 9 by performing a single mouse clicking operation.

Notably, the third illustrative embodiment has been described with particular focus given to CPIR-enabling Applets encoded with the UPN of a particular consumer product. It is understood, however, that the CPIR-enabling Applets of the present invention can be encoded with the trademark(s) used in connection with a particular consumer product, thus providing Trademark-encoded CPIR-enabling Applets, in contrast with UPN-encoded CPIR-enabling Applets. In such alternative embodiments, the encoded trademark would be used to direct a search through the RDBMS server 9, and display the results thereof in a new (independent) Java GUI generated at the point of Applet tag embodiment. Alternatively, a product descriptor associated with a particular product can be encoded within the corresponding CPIR-enabling Applet, used to direct a search through the RDBMS server 9, and display the results thereof in an independent Java GUI generated at the point of Applet tag embodiment.

The Fourth Applet-Driven Method of Accessing and Displaying Categorized UPN/URL Link Menus from the UPN/URL Database Management Subsystem the Present Invention

After providing a brief overview on the system architecture of FIG. 2B4 and the nature of the client-side CPIR-enabling Applets deployed therewithin, the steps associated with Applet-driven CPI-acquisition method of the fourth illustrative embodiment will be described in detail with reference to FIGS. 4K1, 4K2, 4L1 and 4L2.

In general, the method of FIGS. 4K1 and 4IK2, like that of FIGS. 4G1 and 4G2 and 4I1 and 4I2 involves using a client-side CPIR-enabling Applet to automatically conduct a UPN-directed search on the UPN/URL Database Management Subsystem hereof (i.e. RDBMS server 9) in response to a single mouse-clicking operation by the consumer on the HTML tag associated with the CPIR-enabling Applet. In the illustrative embodiment, the CPIR-enabling Applet of the present invention is a program written in the Java™ programming language and has an HTML tag (indicated by <APPLET>) which is designed to be included in an HTML page, much in the same way an image can be included therewithin (in accordance with the HTML 3.2 Specification).

In the method of the second illustrative embodiment, CPIR-enabling Applets are designed to work within a request/response processing model, as shown in FIG. 2B4. In this request/response model, a client subsystem 13 sends a request message to the Java Web Server 11′″ and the server 11′″. responds by sending back a reply message. In the illustrative embodiment, requests come in the form of http, although it is understood that other protocols (e.g. ftp, EDI or a custom protocol) may be used. The request and the corresponding response reflect the state of the client and the server at the time of the request.

When using a Java-enabled browser to view a Web page containing a client-side CPIR-enabling Applet tag <APPLET>, the Applet's compiled class code is automatically accessed from the Java Web Server 11′″ and executed on the client-side of the network connection illustrated in FIG. 2B4. Thus, as shown in FIG. 2B3, the Java-enabled client machine 13 in this network architecture must run a Java-enabled browser program that provides a Java Virtual Machine (JVM) for running/executing Java Applets on the client-side thereof, in much the same way that Java Web Server 11′ must provide a JVM for running Java servlets on the server side thereof, as shown in FIG. 2B1.

With reference to FIG. 2B4, the method of creating, loading, distributing, embedding and executing client-side CPIR-enabling Java Applets in accordance with the principles of the present invention schematically illustrated in FIGS. 4K1, 4K2, 4L1 and 4L2 will now be described below.

As indicated at Block A1 in FIG. 4K1, the first step of the method involves using the Java Applet API to write or otherwise author the source code for a client-side CPIR-enabling Java Applet for each UPN-specified consumer product registered in the RDBMS server 9. In general, the source code for each client-side CPIR-enabling Java Applet (i.e. Applet) will embody one or more of following items of information: (i) the UPN of the particular product on which the CPI search is to be carried out and the search results thereof displayed; (ii) Java classes required for performing a UPN-directed search on the RDBMS server 9 using a Remote Invocation Method (RMI) executed on the Java Web Server 11″″, producing a particular Java GUI for displaying the results obtained from the UPN-directed search; and (iii) license-related information specifying the terms and conditions of the CPIR-enabling Applet license and conditions under which the CPIR-enabling Applet shall operate.

Notably, such license-related information may specify: (1) one or more specific host domains (e.g. www.homedepot.com or www.walmart.com) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (2) one or more general Internet domains (e.g. .com, org., .gov, .int, .mil, .uk, etc.) from which a Web document containing the corresponding Applet tag may launch the CPIR-enabling Applet under a licensing program; (3) the time duration of the licensing period associated with the CPIR-enabling Applet; and (4) any other restrictions set by the associated manufacturer and/or retailer, and/or administrator of the consumer product information system of the present invention, that must be satisfied for a registered CPIR-enabled Applet to operate within a Web-document.

The RMI on Java Web Server 11″″ enables connectivity between Java Web Server 11″″ and the RDBMS Server 9 using the standard Java native method interface (JNI) or the standard JDBC package. At its most basic level, RMI is Java's remote procedure call (RPC) mechanism enabling connectivity to the RDBMS server 9 using native methods. Further details on the RMI are published in the Technical Paper “Java Remote Method Invocation—Distributed Computing For Java” by JavaSoft, set forth at http://www.javasoft.com/marketing/collateral/javarmi.html, incorporated herein by reference.

Notably, the Java source code for each CPIR-enabling Applet will vary depending upon implementation. However, regardless of the particular implementation, it can be expected that each CPIR-enabling Applet designed, for example, to search an (Oracle-based JDBC) RDBMS Server 9 for current UPC/URL list symbolically linked to a specified UPN and thereafter display the results in an independent Java GUI, will typically include Java source code specifying:

-   (1) the importable JDBC classes required by the CPIR-enabling     Applet; -   (2) the importable java classes to be used in the CPIR-enabling     Applet; -   (3) the JDBC driver to be loaded for the Oracle-based RDBMS server     9; -   (4) the connection strings to the RDBMS server 9; -   (5) the CPI query to be executed on the UPN/URL Database, dependent     on the UPN of the associated consumer product and possibly other     search criteria and Applet licensing conditions; -   (6) the Applet tag, its graphical icon or alias to trigger execution     the Applet and its associated CPI query; -   (7) the CPI Search Result GUI to be displayed on requesting client     and its relative location to the associated Applet tag; and -   (8) the operations that will be carried out upon execution of the     CPI query including     -   Boolean search logic to be carried out upon initiation of the         UPN-directed CPI search;     -   if a new connection is required between Java Web Server 11′″ and         the RDBMS server 9;     -   Loading the JDBC driver;     -   Connecting to the RDBMS server 9;     -   Creating a SQL statement based on the specified Boolean search         logic and UPN;     -   Executing the SQL query statement; and         -   Dumping the search results to the CPI Search Result GUI.

When using earlier versions of the HTML Specification (i.e. HTML 3.2 by the World Wide Web Consortium), the source code for each CPIR-enabling Java Applet will adhere to the general syntax of that the HTML 3.2 Specification. Also, if the HTML 4.0 Specification is used, then the source code for each CPIR-enabling Java Applet will adhere to the general syntax of the HTML 4.0 Specification, as discussed above.

After writing/authoring the source code for the CPIR-enabling Java Applet, the Applet is ascribed a unique name such as, for example, “UPNXXXXXXYYYYYZ” for a 12 digit Uniform Product Code.

As indicated at Block A2 in FIG. 4KI, the second step of the method involves compiling the source code of the Applet into Java bytecode, and then placing/loading the classfiles for the Applet within the server_root/Applets directory on the Java Web Server 11″″.

As indicated at Block B1 in FIG. 4KI, the third step of the method involves for each UPN-specified consumer product, (1) containing the complete Applet HMTL tag <APPLET> within an executable file, and (2) storing each such Applet tag containing file in the Central CPIR-Enabling Applet Library on the RDBMS server 9, as shown in FIG. 4J1.

As indicated at Block C in FIG. 4I1, the fourth step of the method involves distributing the CPIR-enabling Applet HMTL tags to retailers, wholesalers, advertisers, and others who desire to deliver UPN-directed CPI search results to their customers, clients and the like. This distribution process may be carried out in several different ways which have been detailed hereinabove in connection with the second illustrative method illustrated in FIGS. 4G1 through 4H2 and described above.

As indicated at Block D in FIG. 4K2, the fifth step of the method involves enabling retailers, wholesalers, advertisers, and others to (1) open the downloaded Applet tag containing files, (2) extract the CPIR-enabling HMTL tags contained therewithin, and (3) embed (i.e. insert) one or more distributed CPIR-enabled Applet tags into acceptable HTML-encoded documents associated with EC-enabled WWW sites, EC-enabled storefronts and catalogs, Internet product advertisements, on-line auction-based WWW sites, or other types of Web-documents.

In general, this step of the method involves first creating or otherwise procuring a suitable HTML-encoded document which may understandably include other types of code (e.g. XML) therein, other than HTML code. While such HTML documents can be created using any HTML-editing program, such as BBD-Edit, it is expected that in most applications the underlying HTML-encoded document will be generated using tools such as, for example: GO-LIVE® WWW-Site Development and Management solution software from Adobe Systems, Inc. to create the HTML pages associated with a particular WWW site; CatalogMaker™™ and CatalogManager electronic commerce solution software programs from RealEDI, Inc; Intershop 4 Enfinity™ Electronic Commerce Solution software from Intershop Communications, Inc; and/or any other commercially available HTML-authoring tools which enable quick and easy creation of HTML-encoded documents, and easy insertion of any downloaded CPIR-enabling Applet HMTL tag using, for example, simple commands or drag-and-drop procedures.

As indicated at Block E in FIG. 4K2, the sixth step of the method involves serving servlet tag encoded HTML documents from Internet information servers to Java-enabled client computer subsystems 13 operated by consumers at home, in the office, in EC-enabled and “brick and mortar” retail stores, or on the road, as the case may be. As shown in FIG. 4H1, such Internet information servers can include, for example, IPI servers 12, retailer-related EC-enabled information servers 12A, manufacturer-related EC-enabled information servers 12B, and/or any other Internet (http or ftp) information servers operating on the Internet from which HTML-encoded document are served for any informational, educational, and/or entertainment purpose.

As indicated at Block F in FIG. 4G2, the seventh step of the method hereof involves using a Java-enabled client computer subsystem 13 to display served HTML-encoded documents having one or more of CPIR-enabling Applet tags embedded therewithin. This step is carried out by the consumer pointing his or her Java-enabled browser program (e.g. Netscape's Navigator, Microsoft's Internet Explorer, or Sun Microsystems' HotJava program) to an HMTL-encoded document within which a CPIR-enabling Java Applet tag is embedded, at a particular point of presence on the WWW. As shown in FIGS. 4M1 through 4R2, CPIR-enabling Applets can be graphically-encoded in an variety of different ways as described in detail detailed hereinabove in connection with the second illustrative method illustrated in FIGS. 4G1 through 4H2 and described above.

As indicated at Block G in FIG. 4G2, the eight step in the method involves the consumer recognizing that a CPIR-enabling Applet tag is embedded within a Web-document displayed on a Java-enabled client computer subsystem, and thereafter launching/executing the associated Applet to initiate a UPN-directed search within the RDBMS server 9 by performing a single mouse clicking operation.

Notably, the third illustrative embodiment has been described with particular focus given to CPIR-enabling Applets encoded with the UPN of a particular consumer product. It is understood, however, that the CPIR-enabling Applets of the present invention can be encoded with the trademark(s) used in connection with a particular consumer product, thus providing Trademark-encoded CPIR-enabling Applets, in contrast with UPN-encoded CPIR-enabling Applets. In such alternative embodiments, the encoded trademark would be used to direct a search through the RDBMS server 9, and display the results thereof in a new (independent) Java GUI generated at the point of Applet tag embodiment. Alternatively, a product descriptor associated with a particular product can be encoded within the corresponding CPIR-enabling Applet, used to direct a search through the RDBMS server 9, and display the results thereof in an independent Java GUI generated at the point of Applet tag embodiment.

While the illustrative embodiments described above have employed Java Applet technology, which is designed to work with nearly all modern Internet browser programs, it is understood, however, that it is possible to use Active-X type objects (i.e. Active-X Applets) embedded within Web-documents, such as XML and SGML encoded documents including Active Server Pages (ASPs) from the Microsoft Corporation, in order to implement UPN-directed methods or the present invention at the point of presence of the consumer within a Cyberspace environment. Such alternative embodiments are a straightforward application of the techniques and technology disclosed hereinabove and thus fall within the scope and spirit of the present invention.

Also, while the above-described method of information searching, access and display has been described in connection with consumer products, it is understood that the principles of the present invention can also be used to deliver Web-based information to consumers in connection with a particular consumer service which has been assigned a Universal Service Number (USN) that functions in a similar manner to a UPN used in connection with a particular consumer product. In such alternative embodiments, the UPN/URL Database Management Subsystem 9 can be readily extended to contain symbolic links between Universal Service Numbers (USN) and URLs to form a UPS/URL database along the principles described hereinabove.

Also, the CPIR-enabling Applets of the present invention may be modified to provide consumers with general access to any IPI WWW site in accordance with the present invention, and not necessarily a product-specific Cyber-Service™ search, as described above. Thus, for example, in the case where the CPIR-enabling Applet is not encoded with any particular UPN, then the CPIR-enabling Applet will generate and display a pop-up Java GUI at the point where its Applet tag (or related image IMG) is embedded. Such as Java GUI could be designed to enable either (1) a generalized (unrestricted) consumer product information display, as would be desired at WWW search Engines/Directories such as Yahoo, Lycos, Excite, Alta-Vista, and the like, or (2) a restricted consumer product information display, as would be desired by a particular retailer operating an EC-enabled store or on-line catalog where browsing for merchandise not carried in the store or catalog is not to be encouraged.

An example of a CPIR-enabling Applet designed to produce a Java GUI for the “manufacturer-unrestricted or generalized” UPC Request CPI Service is illustrated in FIGS. 4N1 and 4Q1 by using a graphical icon or button, displayed on the lower portion of each display screen, and labeled as “UPC REQUEST™ CENTRAL Product Information Search”. An example of the Java GUIs produced by these CPIR-enabling Applets are illustrated in FIG. 4N2 and 4Q2, respectively.

An example of a CPIR-enabling Applet designed to produce a CPID-enabling Java GUI for the “manufacturer-restricted” UPC Request Retailer CPI Service is indicated in FIG. 4O1 by a graphical icon or button, displayed on the lower portion of each display screen, and labeled as “UPC REQUEST™ Retail Product Information @ SPORTS PLACE”. An example of the Java GUI produced by this CPIR-enabling Applet is indicated in FIG. 4O2. Notably, this type of CPIR-enabling Applet provides consumers with desired information about the UPN-encoded product, while disabling the consumer from browsing for merchandise not carried in the EC-oriented store or catalog of the hosting retailer.

As illustrated above, in the case where the CPIR-enabling Applet is encoded with a particular UPN, then the function of the CPIR-enabling Applet will be to generate and display an independent pop-up Java GUI at the point where the Applet tag (or associated image) is embedded, for displaying the search results made against the consumer product identified by the UPN embodied within the CPIR-enabling Applet. An example of a CPIR-enabling Applet designed to produce a CPID-enabling Java GUI for a Cyber-Service URL Search is indicated in FIGS. 4P1 and 4R1 by a graphical icon or button, displayed on the lower portion of each display screen, and labeled as “UPC REQUEST™ Cyber-Service™ URL Search.” Notably, operation of this type of CPIR-enabling Applet can be restricted to a particular retailer (or manufacturer) by the inclusion of a domain name constraint within the Applet itself, as described hereinabove. In the case of the Cyber-Service URL Search of the UPC Request System, the executed CPIR-enabling Applet automatically returns for display a menu of categorized URLs symbolically linked to the encoded UPN by the manufacturer and/or its agent. It would be desirable to embed this type of CPIR-enabling Applet on Web-documents in an EC-enabled stores and on-line catalogs of a particular retailer or manufacturer, displaying consumer products to be purchased, as well as on Web-documents serving as Internet-based product advertisements.

Referring to FIGS. 4N1 and 4N2, the above-described method of CPI searching and display will now be illustrated in the context of browsing a WWW Search Directory or Engine, and looking for a simple yet effective way of finding accurate consumer product related information on a particular product, or class of products. When searching for consumer product information at a WWW Search Directory or Engine, such as Yahoo, Excite, Alta Vista, Lycos, etc., it will be desirable for the consumer to search against all manufacturers within the entire UPN/URL Database Management Subsystem 9 before returning the search results to the consumer for display. Therefore, in this sort of Cyberspace environment, it will be oftentimes desirable to embed a CPIR-enabling Applet in the home-page of the WWW search directory or engine so that, upon clicking the graphical icon thereof, an independent Java GUI to the UPC Request Central WWW site will be automatically produced so that all modes of searching are made available to the consumer against all manufacturers registered (and possibly unregistered) within the UPN/URL Database Management Subsystem 9, as shown in FIG. 4N2. Notably, this Java GUI is very similar to the Java GUI set forth in FIG. 3C.

Referring to FIGS. 4O1 through 4O2, the above-described method of CPI searching and display is illustrated in a different context, wherein a consumer is shopping/browsing an EC-enabled storefront of a particular retailer, and considering whether or not to make an on-line purchase of a particular consumer product displayed within the catalog pages thereof. In this sort of environment, the retailer will typically prefer that the consumer can only search on manufacturers of merchandise being offered for sale within the EC-enabled store, lest the consumer will encouraged to leave upon finding out that what he or she is looking for is available in a different retail store, and not the store at which he or she is present. Therefore, in this sort of Cyberspace environment, it will be oftentimes desirable to embed a CPIR-enabling Applet in the home-page (or other conspicuous locations) of each retailer's WWW EC store so that, upon clicking the graphical icon thereof, an independent Java GUI to the UPC Request Retailer WWW site “@ the retailer store” will be automatically produced so that all modes of searching are made available to the consumer against only those manufacturers registered (and possibly unregistered) with the UPN/URL Database Management Subsystem 9 which supply consumer products for sale within the particular retail store, as shown in FIG. 4O2. Notably, this Java GUI is similar to the Java GUI set forth in FIG. 3C, except that a “manufacturer filter” set by the retailer UPC product catalog is used to filter out the search results displayed on the Java GUI.

Referring to FIGS. 4P1 and 4P2, it can be seen that the consumer within the EC-enabled store shown in FIGS. 4O1 and 4O2 has proceed to look at a particular product in the retail store (e.g. the “Ultralite Dagger Mountain Bike” being offered for sale for $285.00). At this point of presence within the EC-enabled retail store, the consumer might like to review the very best information published wherever on the WWW relating to this particular consumer product. Therefore, in this sort of Cyberspace environment, it will be desirable to embed a CPIR-enabling Applet within or near the image of this product in the retailer's WWW EC store so that, upon clicking the graphical icon thereof, a “UPC Request Cyber-Service URL Search” will be automatically carried out within the UPN/URL Database Management Subsystem 9, and the search results thereof displayed in a Java GUI, as shown in FIG. 4P2. As shown, the Java GUI displays a menu-formatted list of categorized URLs that have been symbolically linked to the UPN of the consumer product on which the search inquiry was initiated. Typically, this menu of URLs, accessed from the UPN/URL Database Management Subsystem 9, would have been updated as early as the night before during UPN/URL link updating/management operations carried out between (i) the UPN/URL catalog maintained in a client computer subsystem 13 within the backoffice of the manufacturer, and (ii) the Manufacturer/Product Registration Subsystem 31, 33, using electronic data interchange processes based on any one of number of protocols (e.g. ftp, EDI, XML/ICE, etc.).

Referring to FIGS. 4Q1 through 4Q2, the above-described method of CPI display is illustrated in the context of a consumer visiting an on-line EC-enabled auction site (e.g. at http://www.ebay.com), and considering whether or not to place a bid on a particular consumer product displayed within the auction listings thereof. In general, this environment is similar to the situation where a consumer finds him/herself searching for consumer product information at a WWW Search Directory or Engine, such as Yahoo, Excite, Alta Vista, Lycos, etc. In such an environment, it will be desirable for the consumer to search against all manufacturers within the entire UPN/URL Database Management Subsystem 11 before returning the search results to the consumer for display. Therefore, in this sort of Cyberspace environment, it will be oftentimes desirable to embed a CPIR-enabling Applet in the home-page of the WWW on-line auction site so that, upon clicking the graphical icon thereof, an independent Java GUI to the UPC Request Central WWW site will be automatically produced so that all modes of searching are made available to the consumer against all manufacturers registered (and possibly unregistered) within the UPN/URL Database Management Subsystem 9, as shown in FIG. 4Q2. Notably, this Java GUI is very similar to the Java GUI set forth in FIG. 3C.

Referring to FIGS. 4R1 and 4R2, it can be seen that the consumer within the on-line auction site shown in FIGS. 4Q1 and 4Q2 has proceed to look at a particular item being auctioned off (e.g. the “Sony Mavica MVC-FD81” at a current bid of $420.50). At this point of presence within the on-line auction site, the consumer might very well like to review the very best information published wherever on the WWW relating to this particular consumer product. Therefore, in this sort of Cyberspace environment, it will also be desirable to embed a CPIR-enabling Applet within or near the title of the product being auctioned (or image thereof if available) so that, upon clicking the graphical icon thereof, a “UPC Request Cyber-Service” URL Search will be automatically carried out within the UPN/URL Database Management Subsystem 9, and the search results thereof displayed in a CPID-enabling Java GUI, as shown in FIG. 4R2. As shown, this Java GUI displays a menu-formatted list of categorized URLs that have been symbolically linked to the UPN of the auctioned consumer product on which the search inquiry was initiated. Typically, this categorized menu of URLs, accessed from the UPN/URL Database Management Subsystem 9, would have been updated as early as the night before during daily UPN/URL link updating/management operations carried out in the manner described hereinabove.

Referring to FIGS. 4S1 through 4S2, the above-described method of CPI searching and display is illustrated in the context of a consumer visiting a typical WWW site (e.g. the Applicant's Intellectual Property Law Firm at http://www.tjpatlaw.com), whereupon an Internet advertisement is presented for a particular consumer product, solely for illustrative purposes. At this point of presence on the WWW, the consumer might very well like to review information published on the WWW relating to the advertised consumer product. Therefore, in this sort of Cyberspace environment, it will also be desirable to embed a CPIR-enabling Applet within, closely near, or immediately about the space of the advertisement so that, upon clicking the image associated thereof, a “UPC Request Cyber-Service” URL Search will be automatically carried out within the UPN/URL Database Management Subsystem 9, and the search results thereof displayed in a CPID-enabling Java GUI, as shown in FIG. 4S2. As shown, this Java GUI displays a menu-formatted list of categorized URLs that have been symbolically linked to the UPN of the advertised consumer product on which the search inquiry was initiated. Typically, this categorized menu of URLs, accessed from the UPN/URL Database Management Subsystem 9, would have been updated as early as the night before UPN/URL link updating/management operations carried out in the manner described hereinabove.

In situations where the advertisement itself embodies a Java-Applet, as in the case of most banner-type advertisements, it would be desirable to embed the CPIR-enabling Applet within the HTML-encoded document displayed within the new Java GUI generated when the Java-Applet is executed by the consumer upon his or her initial encounter of the advertisement. Upon the display of the menu-formatted list of categorized URLs within the CPID-enabling Java GUI, the consumer can easily access different Web-documents containing information related to the advertised consumer product by simply selecting the URL and linking to the information resource to which it points on the WWW. Notably, the displayed URL menu would include (i) one or more URLs pointing to EC-enabled stores and on-line catalogs at which the advertised product can be purchased over the Internet, as well as (ii) one or more URLs pointing to “brick and mortar” type retail stores at which the advertised product can be purchased in the stream of commerce.

Thus, the CPI-based search and display method of the present invention gives rise to a new method of and system for purchasing a consumer product over the Internet (e.g. WWW) comprising the steps of: embedding a UPN-encoded CPIR-enabling Applet within the HTML-code of a consumer product advertisement, wherein the CPIR-enabling Applet when executed displays a categorized URL menu containing one or more URLs pointing to one or more EC-enabled stores or on-line catalogs on the WWW at which the consumer product identified by the encoded UPN can be purchased and delivered to a particular address in physical space.

Overview of Modes of Operation for IPT Finding and Serving Subsystem

In order to enter a primary mode of operation of the IPI Finding and Serving Subsystem, the consumer, retail sales clerk or retailer selects a particular mode activation button (e.g. 21A, 21B, 21C, 21D, 21E, or 21F) displayed in the control frame 21B of the Java GUI browser program at the requesting client subsystem 13. Upon making the selection, the Web browser at the client subsystem 13 automatically requests a particular HTML-encoded form (typically residing on the IPD Server(s) 11). In general, each mode activation button 21A through 21F can be linked to a client-side or server-side Java Applet tag embedded within an HTML-encoded document, or directly to a predefined static-type HTML form corresponding to the selected mode of operation. In the case of Java Applets, upon selecting the mode selection button, a Java GUI is automatically produced and displayed within the information display frame 20C of the Web browser of the requesting client subsystem. In the case of the directly-linked static-type HTML forms, a GUI in the form of HTML document is automatically produced and displayed within the information display frame 20C of the Web browser of the requesting client subsystem. In either case, the HTML-encoded form corresponds to the selected mode and is linked to a Java method (or CGI script) related to the selected mode and possibly to other methods or forms required to carry out the database access and/or management process associated therewith. The requesting client subsystem then enters the information requested by the HTML form displayed within the information display frame 20C of the Web browser's GUI interface. Information entry into the HTML form can be carried out using bar code symbol reading equipment, keyboard or keypad, speech dictation equipment (by Dragon Systems, Inc. of Newton, Mass.), and the like.

In general, the particular messages which will be displayed within the HTML forms during any particular mode of operation will depend upon several factors namely: whether the IPI Web-site is intended for access by bar code driven kiosks (i.e. client subsystems 13) as shown, for example, in FIGS. 3A2, 3A3, 3A4, and 3A5 located within retail environments; or whether the IPI Web-site is intended for access by desktop, laptop and palmtop client computer systems 13 as shown, for example, in FIG. 3A1 located at home, in the office or on the road.

For example, if the IPI Web-site supported by the IPI Finding and Serving Subsystem hereof is intended for access by bar code driven kiosks, then the HTML documents related to the IPI Website will be particularly adapted to facilitate the use of bar code symbol reader at the client subsystem. This way UPNs (e.g. UPC or EAN symbols) can be easily entered into the subsystem without manual key-entry operations. In contrast, if the IPI Web-site supported by the IPI Finding and Serving Subsystem hereof is intended for access by client subsystems not having bar code symbol readers (e.g. Web-enabled computer systems at home, in the office or on the road), then the HTML documents related to the IPI Website will be particularly adapted to facilitate the use of data-entry display screens at the client subsystem. This way, UPNs (e.g. UPC or EAN symbols) can be easily entered into the subsystem using bar code symbol scanners avoiding manual key-entry operations. In the illustrative embodiment, bar code-code driven and manual data-entry IPI Websites are served from a “framed” Java GUI, in which the control strip 20B has six (5) Check Boxes 21A through 21F described above to enable the consumer, retail sales/service personnel as well as manufacturers to select the particular mode of operation that suits his or her consumer product information needs at any particular instance in time.

It understood that the use of Java Applets (including Servlets) will be most beneficial in constructing Java-based IPI Central and retail WWW sites, as indicated above, and in most instances will be preferable over static HTML documents and CGIs linking the IPD (http) server 11 to the backend RBDMS servers 9 of the system. However, for purposes of illustration only, the six primary modes of operation of the system will be described below using a CGI implementation, illustrated in FIG. 2B2. However, it is understood that implementations using CPIR-enabling Servlets as shown in FIG. 2B1 can be used to replace such CGI constructions. Also, implementations using CPIR-enabling Applets as shown in FIGS. 2B3 and 2B4 can be used to enable access to the UPN/URL Database Management Subsystem 9 and its supporting RDBMS servers.

Manufacturer/Product Registration Mode of Operation

Referring to FIG. 5A, the high level structure is shown for a communication protocol that can be used among a client subsystem C_(a), an IPD Server Sb, and an IPI Server Sc of the IPI finding and serving subsystem hereof when it is induced into the Manufacturer/Product Registration Mode of operation from the point of view of the depicted client subsystem. FIG. 6A provides a high level flow chart illustrating the steps involved in carrying out this communication protocol when the IPI Finding and Serving Subsystem is in its Manufacturer/Product Registration Mode of operation.

As indicated at Block A in FIG. 6A, when selected from the user interface of an IPI Website, the first Check Box type button 21A automatically activates the Manufacturer/Product Registration Mode of the IPI Finding and Serving Subsystem by sending an HTTP request to the IPD Server(s) 11″ based on a URL hot-linked to the selected Check Box. As indicated at Block B in FIG. 6A, this causes a HTML-encoded document residing on the IPD Server 11″ shown in FIG. 2B2, to requesting client subsystem 13 or display on the information display frame 20C thereof. The HTML document of the illustrative embodiment displays several types of information relevant to the Manufacturer/Product Registration Mode, namely: eligibility requirements (i.e. qualifications) for a manufacturer to register with the IPI Finding and Serving Subsystem; optional ways of registering consumer products and product-related information with the Manufacturer/Product Registration Subsystem hereof 33; ways of acquiring computer software necessary for managing consumer product-related information (e.g. UPNs, URLs, trademarks and product descriptors) on a particular computing platform using EDI (or XML/EDI) techniques supported by the Manufacturer/Product Registration Subsystem 33; etc; and one or more Check Boxes embodying links (i.e. anchors) to HTML documents, CGI scripts and the like designed to facilitate this mode of operation. Notably, at least one of these HTML documents will be located on the Web Document Server 30 of the Manufacturer/Product Registration Subsystem 33, providing manufacturers (and/or their designated information-managers and agents) with a point of entry into the manufacturer/product registration process hereof. As indicated at Block C in FIG. 6A, the manufacturer and or its agent follow the instructions displayed on the HTML document, linking to the Web Document Server 30 of the Manufacturer/Product Registration Subsystem 33 and filling out the various HTML forms transmitted to the requesting client subsystem, downloading Web-based EDI (or XML/EDI) software for UPN/URL management; and the like. While carrying out registration of manufacturers with the subsystem is relatively straightforward, there are a number of different ways of carrying out the Product Registration Mode of the subsystem. These alternative techniques will be described below.

The first method illustrated in FIGS. 2-1 and 2-2 involves by carrying out FTP between a client subsystem of the registering manufacturer (or its agent) Mi and IPD Server 11″ in order to update the IPI Registrant Database associated therewith. This can be carried out by the manufacturer's officer or agent surfing to the IPI Website, selecting the “Product Registration Mode” from the control strip, and then following the instructions displayed on the various screens of the Website in this mode. When using the first method, product UPCs, URLs and other information elements can be formatted within suitable Product Registration Forms and transmitted by FTP from the client subsystem or Database Server of a registering manufacturer to the IPD Server 11″ so that the IPI Registrant Database thereof can be updated accordingly. The first method will be desirable typically when registering a few consumer-products.

The second method illustrated in FIG. 2A, involves first carrying out EDI between a client subsystem of the registering manufacturer (or its agent) and the UPN/URL Database Subsystem 9, and then carrying out FTP or SMTP between the client subsystem and IPD Server 11″ in order to update the IPI Registrant Database maintained therein. The second method will be desirable when a manufacturer needs or desires to register a large number of consumer-products. The details of these information transmission methods will be described below.

When using the second method, conventional EDI protocols or more modern protocols (e.g. XML/ICE) can be used to transmit product UPCs, URLs and other information elements from client subsystems or database servers of manufactures to the UPN/URL Database Subsystem 9 of the present invention. FTP can be used to transmit UPCs and URLs from the UPN/URL Database Subsystem to each IPD Server in the system so that the IPI Registrant Database thereof can be updated accordingly. Once registered with the system using either of these methods in the Product Registration Mode, such consumer-products can be easily found on the Internet by anyone wishing to use the product finding techniques of the present invention.

The third method involves by carrying out electronic data and document interchange over the Internet between the WebDox Remote™ Computer System 13 and the WebDox™ Server 30 of the system of the present invention, and communication between the WebDox™ Server 30 and the WebDox™ Admin computer system 31 of the system hereof. The various steps involved in this embodiment of the consumer product registration process will be described in detail below.

When the manufacturer selects the “Product Registration Mode” of the system, a Manufacturer Registration Form is automatically downloaded from the WebDox™ Server 30 to the Manufacturer's client computer system 13 (i.e. the WebDox Remote™ Computer System). At the end of the downloading process, a Manufacturer Registration Form is presented (i.e. displayed) and the manufacturer then enters some requested identification information (e.g. Manufacturer's Company Name, Address, Name of CEO and President, phone number, 6-digit Manufacturer Identification Number assigned by the UCC, etc.) and presses the “Send” button on the Manufacturer Registration Form. The form is then transmitted immediately via the Internet and received by the WebDox™ Server 30. At the WebDox™ Server 30, an automated process takes the information in the Manufacturer Registration Form and registers the Manufacturer with the system.

Upon registering the manufacturer with the system, the manufacturer is asked to select which version of “customized” WebDox Remote™ software (i.e. the UPN/URL Registration Application) the manufacturer would like downloaded to its client computer system 13 (e.g. WebDox Remote with UPN/URL Database and CGI scripts for MacOS WebServer, WebDox Remote with UPN/URL Database and CGI scripts for UNIX Web Server, or WebDox Remote with UPN/URL Database and CGI scripts for NT Web Server). Once the manufacturer makes its selection, the customized WebDox Remote software is automatically downloaded to the manufacturer's client computer system 13. This downloaded software includes a computer program that automatically generates (on the manufacturer's) client subsystem, a relational database management system (RDBMS) which allows the manufacturer (or its agents) to easily construct and maintain a UPN/URL database (akin to that specified in FIG. 4A1) but restricted to containing information relating only to the manufacturer's products. Thus, when the manufacturer attempts to enter a UPC number into the manufacturer's UPN/URL database that does not contain the 6-digit Manufacturer Identification Number assigned to the manufacturer by the UCC, the RDBMS automatically blocks all such information entries. Consequently, the UPN/URL database can only maintain information pertaining to the registered manufacturer's products and information relating thereto on the Internet. As the manufacturer adds or removes products from its retail or wholesale line, the database administrator simply adds or removes the UPC and URL information relating thereto from the RDBMS. As will be described in greater detail hereinafter, such database changes are periodically transmitted to the WebDoX™ Server 30 so that the IPI Registrant Database (i.e. master UPN/URL database) of the system (maintained on the IPD Servers thereof) can be updated in a timely manner.

Preferably, the limited or restricted version of the UPN/URL database maintained by each registered manufacturer on its client subsystem 13 is connected to the manufacturer's Internet Server 12′ (or 12B) by a CGI script or Java method, as shown in FIGS. 2-1 and 2-2. In this way, the manufacturer's limited version of the UPN/URL database can be made accessible to consumers world-wide from the manufacturer's Website which, in the illustrative embodiment, is assumed to be hosted on an Internet information server 12′ or 12B that is similar to an IPI Server 12 described in detail hereinabove. In order to simply the process of serving of the manufacturer's limited-version of the UPN/URL database on the WWW, it is preferred that the CGI script 40, input forms, output forms, and methods for searching and the displaying the results from the limited-version UPN/URL database are predesigned for use with manufacturer's Internet Server 12′ (taking into consideration its operating system and the like). This way, prior to registration the manufacturer need only make a selection of the type of customized WebDox Remore software it needs for its computing and Internet serving platform(s). Then, during software download, the WebDox Server 30 simply transmits the suitable version of the customized WebDox Remote software to the manufacturer so that it can create, maintain and serve (on the WWW) its limited version of the UPN/URL database in a “turn-key” manner.

In the illustrative embodiment of the present invention, the homepage of each registered manufacturer's Website will display a visually conspicuous radio button labeled “UPC Request™ Product Finder” or the like. Moreover, whenever a consumer attempts to search the manufacturer's limited-version UPN/URL database for products not registerable to the manufacturer (i.e. using UPC numbers not containing the manufacturer's 6-digit UCC Manufacturer Identification Number), the limited-version of the UPN/URL database will automatically display an HTML-encoded message from the manufacturer's Website, urging the consumer to surf to the IPI Registrant Database of the system (maintained on the network of IPD servers 11). Preferably, such HTML-encoded messages will have a hot-linked URL (i.e. anchor) to Website(s) providing consumer access to the “master” UPN/URL database.

The WebDox Remote™ computer system 13 available to each registered manufacturer has both online and offline modes of operation. In the offline mode, the manufacturer responds to a UPN/URL Registration Request from the WebDox™ Server in the following manner. First, the WebDox Remote™ software analyzes the limited-version of the UPN/URL database that it has been currently created and maintained by the manufacturer or its designee. Thereafter, the WebDox software automatically creates a UPN/URL Registration Response document which contains a set of currently active URLs specifying the address location of Web-based information resources associated with each UPC-encoded product of the manufacturer. Then, WebDox Remote™ program establishes an Internet connection with the WebDox™ Server, through a “Get/Send Mail” option. This delivers the UPN/URL Registration Response (document) to the WebDox™ Server 30 and retrieves any documents which are waiting thereat for the manufacturer. These new documents are listed by WebDox Remote™ program and presented in the InBasket of the manufacturer's WebDox Remote™ computer system 13.

In the online mode, WebDox Remote™ (under the control of the Form Application) can also send UPN/URL Registration Request documents immediately. For very sensitive applications (i.e. Just-in-Time), this ensures that the UPN/URL Registration Response document is received at the WebDox™ Server 30 the moment that the manufacturer completes the document.

In general, the WebDox™ Server 30 provides a high-volume document processing and mailboxing environment between the WebDox Server and the WebDox Remote™ system of each registered manufacturer. WebDox™ Server 30 performs: permanent storage and tracking of all UPN/URL Registration Request documents sent and UPN/URL Registration Response documents received; automatic reconciliation of acknowledgments from WebDox Remote™ program; automatic creation of user-friendly receipt messages to the manufacturer; “mailboxing” of outbound UPN/URL Registration documents for retrieval by manufacturer; and automatic manufacturer and profile creation based on forms received from manufacturers. The WebDox™ Server 30 consists of online components that run as extensions to Microsoft's Internet Information Server (IIS) using the ISAPI interface. This provides higher performance and lower hardware requirements than a conventional CGI Web Interface. Processing intensive tasks are performed asynchronously from the Web server. An integrated queuing and dispatching system manages the processing of documents and interaction with the corresponding application. For large volume situations, the WebDox™ Server components can be deployed on different machines, the WebDox™ Server components (ISAPI extensions) on one machine, the processing components and database on another machine.

Data for UPN/URL Registration Request documents to be sent to manufacturers is extracted from the IPI Registrant Database using an interface or utility program. The document data (e.g. information fields associated with UPN/URL registration) can then be accepted by WebDox in a direct manner after formatting. The UPN/URL Registration Request document should be formatted to a file structure created during the design of the UPN/URL Registration Application. The WebDox™ Server 30 then converts the application data into a UPN/URL Registration request document (i.e. data package). The data package for each manufacturer is then stored (as a message) in an assigned Mailbox of the WebDox™ Server 30. These messages are then available to be retrieved by the registered manufacturers using WebDox Remote's™ “Get/Send Mail” feature.

As discussed above, the WebDox Remote™ program transmits messages (e.g. UPN/URL Registration Response documents) to the WebDox™ Server 30, where, after passing security checks, they are placed in the WebDox Mailbox system. Incoming (document) messages are received from the Mailbox, processed, and converted into data files for direct transfer to the database management system handling the IPI Registrant Database.

For each document received, the WebDox™ Server 30 will return a message to the manufacturer confirming receipt of the document. WebDox Remote™ system also returns delivery confirmations to the WebDox Server. These messages are used by the WebDox™ Server to track the status of messages. WebDox™ Server 30 maintains Mailbox Files for all inbound and outbound messages. The status of messages is updated on an ongoing basis as acknowledgement messages are received, allowing timely and precise audits. WebDox Admin™ Computer system 31 provides an easy-to-use tool to manage the community of manufacturers, review the status of documents, and configure the WebDox™ Server 30, including: ad hoc maintenance of manufacturer information; online display of the Mailbox permitting inquiry into document status or document activity for particular manufacturers, and the ability to reset document status; creation and maintenance of UPN/URL Registration Profiles; preparation of “releases” of new and updated UPN/URL Registration Applications; Distribution of new and updated UPN/URL Registration Applications; and automatic inventory and tracking of UPN/URL Registration Applications distributed to manufacturers.

In the preferred embodiment, UPN/URL Registration Application design and development is carried out on a Windows 95 or NT workstation. The UPN/URL Registration Application is developed, tested, and then fully implemented for production with manufacturers. New or updated UPN/URL Registration Applications are registered with the WebDox Admin™ computer system 31 and are then distributed to the manufacturers as described herein above.

In the preferred embodiment, UPN/URL Registration Applications are developed using Microsoft Visual Basic™ and related software tools. These products provide rapid design and creation of the screen-based forms that the manufacturer uses. In addition, the “intelligence” behind the form, in the UPN/URL Registration Application, can be very powerful, making the manufacturer's work easier while ensuring that the user and Server application receive high quality data.

The WebDox Admin™ system handles the distribution of UPN/URL Registration Applications to manufacturers. New UPN/URL Registration Applications can be sent to some or all of the existing manufacturers assigned UPC Manufacturer Identification Numbers. Updates to UPN/URL Registration Applications can be sent to manufacturers who are currently using that UPN/URL Application. The actual update is distributed by sending a small notification message to each manufacturer, which then results in the remote site downloading the new forms from the WebDoX™ Server 30, as hereinbefore described above.

Notably, the WebDoc™ Solution has been described above provides one way and means of implementing a method of electronic data and document interchange between client machines of manufacturers and the IPI Registrant Database (i.e. master UPN/URL database in subsystem 9) of the system of the present invention. It is understood, however, that many different types of electronic data interchange solutions (e.g. XML or XML/EDI) can be used to practice the system and method of UPN/URL database management in an efficient and timely manner so that consumers will always be provided with up-to-date URL links on the Internet. For example, the new CenterStage 4 Application Suite from On Display, Inc. of San Ramon Calif., can be used to enable XML-based electronic data interchange (i.e. transfer) between the client computer subsystems 13 operated within the backoffices of manufacturers, and the IPI Registrant Database (i.e. master UPN/URL database) of the system hereof operated in the backoffice of the system administrator. Manufacturers (i.e. vendors) can format their data transactions in any of the many new languages of electronic-business (e.g. cXML, RosettaNet, CBL, BizTalk, OBI, ICE proprietary formats, or standard EDI formats such as ANSI X12), and the CenterStage 4 platform will automatically convert their transactions into the chosen formats of the system administrator responsible for managing the master UPN/URL database.

For further details on the use of electronic data interchange technologies in order to realize this functionality of the system of the present invention, reference can be made to the following technical publications: “XML/EDI: Cyber Assisted Business in Practice” (1999) by Dick Raman (ISBN: 90-8050233-2-1); The A to Z of EDI and Its Role in E-Commerce” Second Edition, 1998) by Nahid Jilovec, published by Duke Communications, Inc., Loveland, Colo.; “Electronic Commerce With EDI: A Guide For Decision Makers” (1998), by Robert L. Sullivan, published by Twain, Inc. North Andover, Mass.; and “Wild's WWW: Technical Foundations of the World Wide Web” (1999) by Erik Wilde, published by Springer-Verlag, Berlin, Heidelberg; each said publication incorporated herein by reference as of set forth herein.

In FIG. 2C, there is disclosed a novel distributed method of collecting, managing and transmitting UPN/URL menus for consumer products. Notably, this distributed system and method will be useful in large corporate environments, where departmentalization is the general rule. As shown, instead of each manufacturer having a single EDI-enabled workstation (equipped with EDI or EDI/XML software) 13 for carrying out UPN/URL management operations, a group of EDI-enabled client computers 13 are connected to a local or wide area network 200 via a network-centric Web (http) server 133 using a network router 201 to interface with the infrastructure of the Internet, as well as the other local or wide area network 200 as shown in FIG. 2C. Preferably, each client computer 13 on the LAN or WAN is equipped with UPN/URL management software for managing the consumer product information collected in the UPN/URL Database for a particular manufacturer, as shown in FIGS. 4A1 through 4B.

In one arrangement, each manufacturer-operated client machine 13 would be assigned the task of managing the UPN/URLs associated with a particular department of the manufacturer (e.g. engineering department, sales department, service/support department, marketing department, advertising department, etc.). The UPN/URLs menus and other CPI related information collected by each department is maintained within a local UPN/URL Database 202 on the department's client machine 13, and is periodically transmitted to a Manufacturer's UPN/URL Database 203 hosted on the network Internet server 133 In addition to providing the client machine behind the corporate firewall with http, e-mail and ftp services, the network Internet server 133 is also equipped with an EDI (e.g. EDI or XML/ICE) software solution which enables periodic uploading of the manufacturer's UPN/URL Database 203 to the Central UPN/URL Database Management Subsystem 9, shown in FIG. 2C.

Another arrangement, each manufacturer-operated client machine 13 would be assigned the task of managing the UPN/URLs associated with a particular department of the manufacturer (e.g. engineering department, sales department, service/support department, marketing department, advertising department, etc.). The UPN/URLs menus and other CPI related information collected by each department is maintained within a local UPN/URL Database 202 on the department's client machine 13, and is periodically transmitted directly to the Central UPN/URL Database Management Subsystem 9, shown in FIG. 2C. In such an alternative embodiment of the present invention, the network Internet server 133 would provide each client machine behind the corporate firewall with http, e-mail and ftp services in a conventional manner, but not maintain a central manufacturer's UPN/URL database 202.

The primary advantage of the above described techniques for distributed UPN/URL management hereof is that such techniques provide manufacturers with a revolutionary way of am and means for enlisting the different departments within the organization, having different business perspectives, goal and resources, to create “up-to-date” links between UPN's on their consumer products and the diverse types of consumer related information resources published on the Internet, all in concerted effort to achieve the sales, marketing and support programs of the company in a unified manner. Using the system and method of the present invention, symbolic links between the manufacturer' products and published information resources on the Internet (e.g. WWW) can be impressed upon the minds of consumers as they seek access to such current information at home, in the office, in physical and electronic stores, as well as on the road.

Manufacturer Website Search Mode of Operation

Referring to FIG. 5B, the high level structure is shown for a communication protocol that can be used among a client subsystem C_(a), an IPD Server Sb, and an IPI Server Sc of the IPI finding and serving subsystem hereof when it is induced into the Manufacturer Website Search Mode of operation from the point of view of the depicted client subsystem. FIG. 6B provides a high level flow chart illustrating the steps involved in carrying out this communication protocol when the IPI Finding and Serving Subsystem is in its Manufacturer Website Search Mode of operation.

As indicated at Block A in FIG. 6B, when selected from the user-interface of a bar-code driven IPI Website, the second Check Box type button 21B automatically activates the Manufacturer Website Search Mode of the IPI Finding and Serving Subsystem by sending an HTTP request to the IPD Server(s) 11″ based on a URL hot-linked to the selected Check Box.

As indicated at Block B in FIG. 6B, this causes a particular type of HTML-encoded document (i.e. called an “HTML form” or “Web form document”) residing on the IPD Server(s) 11″ to be sent to the Web browser of the requesting client subsystem 13 and displayed on the information display frame 20C thereof (requesting this mode of service). As in the Manufacturer Website Search Mode described above, the HTML form sent in the Manufacturer Website Search Mode may also use any HTML format commands, such as headers, paragraphs, and lists, but must include three unique items, namely: the METHOD by which the user input is to be sent; the ACTION, which specifies a URL to which the user input is to be sent, presumably, the IPD Server 11″ that will act upon the request appropriately; and a SUBMIT button, to send the completed form over the Internet via HTTP. In the illustrative embodiment, user input (i.e. a UPC or EAN number associated with a particular consumer product) is obtained by an Input Box, which allows the user (i.e. retail sales clerk or consumer) to type in or scan in a UPC or EAN number assigned to a consumer product on which product related information is sought.

As indicated at Block C in FIG. 6B, the consumer or retail clerk scans the bar coded consumer product, or enters the UPC or EAN number thereon into the Input Box of the HTML form, and selects the SUBMIT button thereon. In response thereto, the Web browser on the client subsystem 13 sends a GET request to the IPD server 11B″ shown in FIG. 2B2. When selecting the SUBMIT button on the HTML form, the Web browser executes the METHOD associated with the HTML form and sends the stored UPC (or EAN) value to the URL specified by ACTION associated with the HTML form (i.e. the Web browser performs the action specified in the ACTION). The ACTION of the HTML form specifies the URL of the CGI script within the http server 11″ that will process the request from the HTML form. This amounts to the Web browser constructing a GET request for that URL, with the arguments (the query string) being attached to the end of the URL. The arguments of the HTML form are specified by the INPUT items of the HTML form (i.e. the UPC or EAN number on the consumer product on which information is sought).

In general, the HTTP and HTML protocols provide three ways to pass the input (e.g. UPC or EAN number) from the users to CGI scripts on the IPD Server 11 (i.e. HTTP Server). All three CGI scripts accomplish the same thing: they allow the Web browser to pass information to the IPD Server 11″.

As indicated at Block D in FIG. 6C, the HTTP (httpd) program on IPD server 11″ passing the arguments (the UPC or EAN numbers in the query string) to the CGI script thereon and the CGI script translates the query string into a proper query for use in searching the RDBMS 9 shown in FIG. 2B2.

As indicated at Block E in FIG. 6C, the translated query is used to search the RDBMS 9 in order to find the set of URLs pointing to HTML documents (i.e. Web Pages) published on the Internet and containing information relating to the consumer product having the input UPC or EAN number. The result returned from the RDBMS 9 is an ASCII record specifying the set of URLs pointing to HTML documents published on the Internet and containing information relating to the consumer product having the input UPC or EAN number entered into the HTML form. In order for the Web browser of the requesting client subsystem to display the results of the database search using the UPC or EAN input, the ASCII record must be converted into a HTML document (i.e. output HTML form). As indicated at Block F in FIG. 6B, the IPD Server 11″ creates the elements of an output HTML form (Web output form), inserts the result from the RDBMS 11″ into the output form, and sets the Content-type to be text/html. The CGI script may translate, filter, augment and reformat the result from the database search in any way so long as the result is an HTML document or some format that the Web browser of the client subsystem can display.

As indicated at Block G, the menu of URLs retrieved from the database search is displayed in the Web output form. At Block H, the consumer or retail sales clerk can link to a desired consumer product related information resource (HTML document) by selecting from the information menu, the URL anchored to the information resource in the displayed information menu.

UPN-Directed Information Access Mode of Operation

Referring to FIG. 5C, the high level structure is shown for a communication protocol that can be used among a client subsystem Ca, an IPD Server Sb, and an IPI Server Sc of the IPI finding and serving subsystem hereof when it is induced into the UPN-Directed Information Access Mode of operation from the point of view of the depicted client subsystem. FIG. 6C provides a high level flow chart illustrating the steps involved in carrying out this communication protocol when the IPI Finding and Serving Subsystem is in its UPN-Directed Information Access Mode of operation.

As indicated at Block A in FIG. 6C, when selected from the user-interface of an IPI Website, the third Check Box type button 21C automatically activates the UPN-Directed Information Access Mode of the IPI Finding and Serving Subsystem by sending an HTTP request to the IPD Server(s) 11 based on a URL hot-linked to the selected Check Box.

As indicated at Block B in FIG. 6C, this causes a particular type of HTML-encoded document (i.e. called an “HTML form” or “Web form document”) residing on the IPD Server(s) 11″ to be sent to the Web browser of the requesting client subsystem 13 and displayed on the information display frame 20C thereof (requesting this mode of service). As in the Manufacturer Website Search Mode described above, the HTML form sent in the UPN-Directed Information Access Mode may also use any HTML format commands, such as headers, paragraphs, and lists, but must include three unique items, namely: the METHOD by which the user input is to be sent; the ACTION, which specifies a URL to which the user input is to be sent, presumably, IPD Server 11′ that will act upon the request appropriately; and a SUBMIT button, to send the completed form over the Internet via HTTP. In the illustrative embodiment, user input (i.e. a UPC or EAN number associated with a particular consumer product) is obtained by an Input Box, which allows the user (i.e. retail sales clerk or consumer) to type in or scan in a UPC or EAN number assigned to a consumer product on which product related information is sought.

As indicated at Block C in FIG. 6C, the consumer or retail clerk scans the bar coded consumer product, or enters the UPC or EAN number thereon into the Input Box of the HTML form, and selects the SUBMIT button thereon. In response thereto, the Web browser on the client subsystem 13 sends a GET request to the IPD Server 11″ shown in FIG. 2B2. When selecting the SUBMIT button on the HTML form, the Web browser executes the METHOD associated with the HTML form and sends the stored UPC (or EAN) value to the URL specified by ACTION associated with the HTML form (i.e. the Web browser performs the action specified in the ACTION). The ACTION of the HTML form specifies the URL of the IPD SERVER 11 that will process the request from the HTML form. This amounts to the Web browser constructing a GET request for that URL, with the arguments (the query string) being attached to the end of the URL. The arguments of the HTML form are specified by the INPUT items of the HTML form (i.e. the UPC or EAN number on the consumer product on which information is sought).

As indicated at Block D, the IPD server 11″ passes the arguments (the UPC or EAN numbers in the query string) to a CGI script running therewithin which translates the Web query string into a proper query to the RDBMS 9 shown in FIG. 2B1.

As indicated at Block E, the translated query is used to search the RDBMS 11A and find the set of URLs (i) linked to the registered consumer product (by the manufacturer or agent thereof) assigned the UPC or EAN number entered into the Input Box of the HTML form, and (ii) pointing to HTML documents on the WWW containing particular types of consumer product related information. The result returned from the RDBMS 9 is an ASCII record specifying the set of URLs satisfying the above criteria. In order for the Web browser of the requesting client subsystem to display the results of the database search during this mode, the ASCII record must be converted into a HTML document (i.e. Web output form).

As indicated at Block F, a CGI script within IPD server 11″ creates the elements of an HTML document (Web output form), inserts the result from the RDBMS 9 into the Web output form, and sets the Content-type of this HTML document to text/html. In the illustrative embodiment, when the Web output form is displayed by the requesting client subsystem, a set of URLs categorized by particular product information types is displayed on the information display frame 20C. Notably, this set of URLs points to particular types of consumer product related information registered within the RDBMS 9 of the system.

As indicated at Block G, the consumer or retail sales clerk can then access and display any HTML document (Web page) located at a particular URL within the information menu by selecting the same using a touch screen, mouse, or other input selection device.

Trademark-Directed Search Mode of Operation

Referring to FIG. 5D, the high level structure is shown for a communication protocol that can be used among a client subsystem Ca, an IPD Server Sb, and an IPI Server Sc of the IPI finding and serving subsystem hereof when it is induced into the Trademark-Directed Search Mode of operation from the point of view of the depicted client subsystem. FIGS. 6D1 through 6D23, taken together, provides a high level flow chart illustrating the steps involved in carrying out this communication protocol when the IPI Finding and Serving Subsystem is in its Trademark-Directed Search Mode of operation.

As indicated at Block A in FIG. 6D1, when selected from the user-interface of an IPI Website, the fourth Check Box type button 21D automatically activates the Trademark-Directed Search Mode of the IPI Finding and Serving Subsystem by sending an HTTP request to the IPD Server(s) 11″ based on a URL hot-linked to the selected Check Box.

As indicated at Block B in FIG. 6D1, this causes a particular type of HTML-encoded document (i.e. called an “HTML form” or “Web input form document”) residing on the IPD Server(s) 11″ to be sent to the Web browser of the requesting client subsystem 13 and displayed on the information display frame 21C thereof (requesting this mode of service). As in the UPN-Directed Information Access Mode described above, the HTML form sent in the Trademark-Directed Search Mode may also use any HTML format commands, such as headers, paragraphs, and lists, but must include three unique items, namely: the METHOD by which the user input is to be sent; the ACTION, which specifies a URL to which the user input is to be sent, (e.g. a CGI script running within http server 11″ that will act upon the request appropriately); and a SUBMIT button, to send the completed form over the Internet via HTTP. In the illustrative embodiment, user input (i.e. the trademark or tradename used with a particular consumer product on which information is sought) is obtained by an Input Box, which allows the user (i.e. retail sales clerk or consumer) to type in the trademark or tradename believed or otherwise known to be used in connection with a particular consumer product on which information is sought.

As indicated at Block C in FIG. 6D1, the consumer or retail clerk enters the trademark or tradename into the Input Box of the HTML form, and selects the SUBMIT button thereon. In response thereto, the Web browser on the client subsystem 13 sends a GET request to the IPD server 11″ shown in FIG. 2B2. When selecting the SUBMIT button on the HTML form, the Web browser executes the METHOD associated with the HTML form and sends the stored trademark value to the URL specified by ACTION associated with the HTML form (i.e. the Web browser performs the action specified in the ACTION). The ACTION of the HTML form specifies the URL of the CGI script running within the IPD server 11″ that will process the request from the HTML form. This amounts to the Web browser constructing a GET request for that URL, with the arguments (the query string) being attached to the end of the URL. The arguments of the HTML form are specified by the INPUT items of the HTML form (i.e. the trademark or tradename used in connection with the consumer product on which information is sought).

As indicated at Block D in FIG. 6D1, the IPD server 11″ passes the arguments (the trademark or tradename in the query string) to a CGI script running therewithin and the CGI script translates the Web query string into a proper query to the RDBMS 9, as shown in FIG. 2B2.

As indicated at Block E in FIG. 6D1, the translated query is used to search the RDBMS 9 in order to find all registered consumer products having product descriptions (PD) registered within the RDBMS 9 that are related to the trademark or tradename entered into the Input Box of the HTML form. The result returned from the RDBMS 9 is an ASCII record specifying each triplet data set (Product Description, UPN and Manufacturer) which satisfies the above trademark search criteria (to a particular degree) entered into the Input Box of the HTML form. In order for the Web browser of the requesting client subsystem to display the results of the database search during this mode, the ASCII record must be converted into another HTML form for use in refining the consumer product information display.

At Block F in FIG. 6D2, a CGI script within IPD server 11″ creates the elements of another HTML document (Web auxiliary input form), inserts the preliminary search result from the RDBMS 9 into the Web auxiliary input form, and sets the Content-type of this HTML document to text/html. In the illustrative embodiment, the Web auxiliary-input form has an ACTION which specifies the URL of a CGI script within the IPD server 11″ that will act upon the request appropriately as if the system were in the UPN-Directed Information Access Mode. The Web auxiliary input form includes an Input Box listing all triplet data sets (i.e. Product Description, Manufacturers and UPN number) satisfying the input trademark search criteria entered in the primary Web input document, described hereinabove. The qualifying triplets listed in the Input Box are provided with a Radio-Button to allow the consumer or retail sales clerk to select one of the triplets from the list thereof for use in a subsequent refined search of the RDBMS 9. The Web auxiliary-input form also has a SUBMIT button for sending the HTML form back to the IPD server 11″ for processing.

As indicated at Block G in FIG. 6D2, when the consumer or retails sales clerk makes a selection with the Radio-Button and then selects the SUBMIT button, the Web browser on the client subsystem 13 sends a request to the HTTP program on the IPD server 11″ to get the completed HTML form.

As indicated at Block H in FIG. 6D2, the HTTP (httpd) program on IPD server 11″ passes the arguments (the trademark or tradename in the query string) to a CGI script running therewithin and the CGI script translates the Web query string into a proper query for use in searching RDBMS 9, as shown in FIG. 2B2.

At Block I in FIG. 6D2, the query is used to search the RDBMS 9 in order to find the set of URLs (i) related to the registered consumer product (by the manufacturer or agent thereof) assigned the UPN, (Product Description and Manufacturer) entered into the Input Box of the HTML (auxiliary) form, and (ii) pointing to HTML (or FTP) documents on the WWW containing particular types of consumer product related information. The result returned from the RDBMS 9 is an ASCII record specifying the set of URLs satisfying the above criteria. In order for the Web browser of the requesting client subsystem to display the results of the database search during this mode, the ASCII record must be converted into an HTML document (i.e. Web output form).

At Block J in FIG. 6D2, the IPD Server 11″ creates the elements of an HTML document (Web output form), inserts the result from the RDBMS 9 into the Web output form, sets the Content-type of this HTML document to text/html, and sends the HTML form to the requesting client subsystem.

At Block K in FIG. 6D3, the set of URLs categorized by particular product information types is displayed within the output HTML form on the information display frame 20C. Notably, this set of URLs points to particular types of consumer product related information registered within the RDBMS 9 of the system by the manufacturer of the product or its agent(s) thereof using the UPN/URL management tools accessible during the Manufacturer/Product Registration Mode hereof.

As indicated at Block L in FIG. 6D3, the consumer or retail sales clerk can access and display any HTML document (Web page) located at a particular URL within the displayed information menu by selecting the same using a touch screen, mouse, or other input selection device available at the requesting client subsystem 13.

Product-Description Directed Mode of Operation

Referring to FIG. 5E, the high level structure is shown for a communication protocol that can be used among a client subsystem Ca, an IPD Server Sb, and an IPI Server Sc of the IPI Finding and Serving Subsystem hereof when it is induced into the Product-Description Directed Mode of operation from the point of view of the depicted client subsystem. FIGS. 6E1 through 6E3 provides a high level flow chart illustrating the steps involved in carrying out this communication protocol when the IPI Finding and Serving Subsystem is in its Product-Description Directed Mode of operation.

As indicated at Block A in FIG. 6E1, when selected from the user-interface of an IPI Website, the fifth Check Box type button 21E automatically activates the Product-Description Directed Search Mode of the IPI Finding and Serving Subsystem by sending an HTTP request to the IPD Server(s) 11″ based on a URL hot-linked to the selected Check Box.

As indicated at Block B in FIG. 6E1, this causes a particular type of HTML-encoded document (i.e. called an “HTML form” or “Web input form document”) residing on the IPD Server(s) 11″ to be sent to the Web browser of the requesting client subsystem 13 and displayed on the information display frame 21C thereof (requesting this mode of service). As in the Trademark-Directed Search Mode described above, the HTML form sent in the Product-Description Directed Search Mode may also use any HTML format commands, such as headers, paragraphs, and lists, but must include three unique items, namely: the METHOD by which the user input is to be sent; the ACTION, which specifies a URL to which the user input is to be sent, (e.g. a CGI script running within the IPD server 11″ that will act upon the request appropriately); and a SUBMIT button, to send the completed form over the Internet via HTTP. In the illustrative embodiment, user input (i.e. the description or descriptor for a particular consumer product on which information is sought) is obtained by an Input Box, which allows the user (i.e. retail sales clerk or consumer) to type in the product description for a particular consumer product on which information is sought.

As indicated at Block C in FIG. 6E1, the consumer or retail clerk enters the product description into the Input Box of the HTML form, and selects the SUBMIT button thereon. In response thereto, the Web browser on the client subsystem 13 sends a GET request to the IPD server 11″. When selecting the SUBMIT button on the HTML form, the Web browser executes the METHOD associated with the HTML form and sends the stored product description to the URL specified by ACTION associated with the HTML form (i.e. the Web browser performs the action specified in the ACTION). The ACTION of the HTML form specifies the URL of a CGI script within the IPD server 11″ that will process the request from the HTML form. This amounts to the Web browser constructing a GET request for that URL, with the arguments (the query string) being attached to the end of the URL. The arguments of the HTML form are specified by the INPUT items of the HTML form (i.e. the product description for the consumer product on which information is sought).

As indicated at Block D in FIG. 6E1, the httpd program on the IPD server 11″ passes the arguments (the product description in the query string) to a CGI script therewithin and the CGI script translates the Web query string into a proper query to the RDBMS 9 shown in FIG. 2B2′.

As indicated at Block E in FIG. 6E1, the translated query is used to search the RDBMS 9 in order to find all registered consumer products having trademarks or tradenames within the RDBMS 9 that are linked to the product description entered into the Input Box of the HTML form. The result returned from the RDBMS 9 is an ASCII record specifying each triplet data set (Trademark, UPN and Manufacturer) which satisfies the above product-description search criteria (to a particular degree) entered into the Input Box of the HTML form. In order for the Web browser of the requesting client subsystem to display the results of the database search during this mode, the ASCII record must be converted into another HTML form for use in refining the consumer product information display.

At Block F in FIG. 6E2, the IPD server 11″ creates the elements of another HTML document (Web auxiliary input form), inserts the preliminary search result from the RDBMS 9 into the Web auxiliary input form, and sets the Content-type of this HTML document to text/html. In the illustrative embodiment, the Web auxiliary-input form has an ACTION which specifies the URL of a CGI script within IPD server 11″ that will act upon the request appropriately as if the system were in the UPN-Directed Information Access Mode. The Web auxiliary input form includes an Input Box listing all triplet data sets (i.e. Trademark, Manufacturer, and UPN number) satisfying the input product-description search criteria entered in the primary Web input document, described hereinabove. The qualifying triplets listed in the Input Box are provided with a Radio-Button to allow the consumer or retail sales clerk to select one of the triplets from the list thereof for use in a subsequent refined search of the RDBMS 9. The Web auxiliary-input form also has a SUBMIT button for sending the HTML form back to the IPD server 11″ for processing.

As indicated at Block G in FIG. 6E2, when the consumer or retails sales clerk makes a selection with the Radio-Button and then selects the SUBMIT button, the Web browser on the client subsystem 13 sends a request to the IPD server 11″.

As indicated at Block H in FIG. 6E2, the httpd program on the IPD server 11″ passes the arguments (the product description in the query string) to a CGI script therewithin and the CGI script translates the Web query string into a proper query for use in searching RDBMS 9 shown in FIG. 2B2.

At Block I in FIG. 6E2, the query is used to search the RDBMS 9 in order to find the set of URLs (i) linked to the registered consumer product (by the manufacturer or agent thereof) assigned the UPN, (Trademark and Manufacturer) entered into the Input Box of the HTML (auxiliary) form, and (ii) pointing to HTML (or FTP) documents on the WWW containing particular types of consumer product related information. The result returned from the RDBMS 9 is an ASCII record specifying the set of URLs satisfying the above search criteria. In order for the Web browser of the requesting client subsystem to display the results of the database search during this mode, the ASCII record must be converted into a HTML document (i.e. output HTML form).

At Block J in FIG. 6E2, the IPD server 11″ creates the elements of an output HTML form, inserts the result from the RDBMS 9 thereinto, and sets the Content-type of this HTML document to text/html and sends a request to the IPD server 11″ to get the HTML form.

At Block K in FIG. 6E3, the set of URLs categorized by particular product information types is displayed within the output HTML form on the information display frame 20C. Notably, this set of URLs points to particular types of consumer product related information registered within the RDBMS 9 of the system by the manufacturer of the product or its agent(s) thereof using the UPN/URL management tools accessible during the Manufacturer/Product Registration Mode hereof.

As indicated at Block L in FIG. 6E3, the consumer or retail sales clerk can access and display any HTML document (Web page) located at a particular URL within the displayed information menu by selecting the same using a touch screen, mouse, or other input selection device available at the requesting client subsystem 13.

The protocols described above can be realized using any suitable programming language including, for example, an object-oriented programming language such as the Java™ programming language.

CPIR-Enabling Applet Download/Distribution Mode of System Operation

As illustrated in FIGS. 4F1, 4F2, 4H1, 4H2, 4J1, 4J2, 4L1 and 4L2, a centralized Library of CPIR-enabling Applets/Servlets is created, management and stored within the UPN/URL Database Management Subsystem 9 hereof in accordance with the above-described methods. In accordance with the principles of the present invention, these CPIR-enabling Applets/Servlets must be widely distributed to retailers, manufacturers, advertisers and others about i the globe and thereafter widely embedded within HTML-encoded documents, as taught in detail hereinabove, to practice this aspect of the present invention in a commercially successful manner. The function of the CPIR-enabling Applet Download/Distribution mode of operation of the system is to enable the world-wide distribution of this centralized Library of CPIR-enabling Applets/Servlets, in accordance with the licensing program associated with each such CPIR-enabling Applet.

As shown in FIG. 3C, the CPIR-enabling Applet Download/Distribution mode is automatically initiated by the user depressing mode control button 21F displayed on the control panel 20B of the UPC Request (Central or Retail) GUI of the illustrative embodiment, but certainly elsewhere in practice. The user can be anyone with the requisite authority to use the Applets in accordance with the terms of the licensing program to be enforced in connection therewith. Understandably, the terms of such licensing programs will be based on prevailing business conditions and will vary from embodiment to embodiment of the present invention.

As best illustrated in FIG. 4F2, upon entering the UPC-Encoded-Applet-Download/Distribution mode, the IPD server 11 of the illustrative embodiment will serve a custom Java GUI as shown in FIGS. 4M1 and 4M2, for carrying out Applet tag downloading and licensing procedures. The GUI will provide (1) links to the centralized Library of CPIR-Enabling Applets/Servlets maintained within the UPN/URL Database Management Subsystem 9, as well as (2) launchable GUIs for downloading selected UPN-identifiable CPIR-enabling Applets to specified Internet-enabled client computer subsystems 13 or Internet information/application servers operated by the user interfacing with this mode of system operation. Notably, electronic data interchange/exchange processes (e.g. based on EDI, XML/ICE or other protocols) can be used to carry out the downloading of CPIR-enabling Applets and other files between client computers and the IPD server 11 during this and other modes of operation.

For licensing purposes, it may be desirable or necessary to have the user supply “end-use” types of information to the IPD server 11 during this mode of operation in order to identify on which information servers or domains (e.g. www.ipfcorp.com) particular CPIR-enabling Applets are to be used (i.e. embedded within HTML-documents and launched therefrom by the end-user which will typically be the consumer). In some instances, licenses for CPIR-enabling Applets will carry a fee to be paid by the downloader; in other instances, there will be no fee requirements. Such details will depend on prevailing business conditions along the retail supply and demand chain.

Once a user has downloaded CPIR-enabling Applets onto a designated (target) client machine or server, the user will have built a local Library (or Catalog) of CPIR-enabling Applets for use during Applet embedding operations which will typically be carried out alongside of other HTML-code authoring and management operations involving, for example, the design, construction, management and maintenance of Web-pages, EC-stores, on-line (retail and wholesale) product catalogs, on-line auction site pages, Web advertisements, and the like.

As shown in FIG. 4F2, during Step D1 of the Applet embedding process, CPIR-enabling requests are accessed from the local Library of CPIR-enabling Applets typically over an IP-type local area network (LAN) or wide area network (WAN). Then during Step D2, the accessed CPIR-enabling Applet is inserted within the HTML code of the target document. This step of the process will typically involve use of HTML-editing tools of one sort or another, as discussed herein above.

Once the CPIR-enabling Applet has been embedded within the target HTML-encoded documents, the HTML-encoded can then be published in its intended publishing environment so that consumers can instantly initiate UPN-directed searches within the centralized UPN/URL Database Management Subsystem 9 hereof by clicking on the CPIR-enabling Applet, and thereafter display the search results within an independent Java GUI which performs the function of a “cyber-kiosk” provided at the consumer's point of presence on the WWW.

Accessing the Modes of Operation of the IPI Finding System Hereof by Launching CPIR-Enabling Applets Embedded Within HTML-Encoded Documents Associated With Electronic-Commerce Enabled Stores and Product Catalogues, Internet Advertisements, On-Line WWW Auction Sites, and the Like

As described in detail hereinabove, a consumer can automatically produce a CPID-enabling Java GUI (i.e. “cyber-kiosk”) by clicking upon a CPIR-enabling Java Applet that has been embedded within the HTML code of any Web-document. As illustrated in FIGS. 4N2, 4O2, 4P2, 4Q2, 4R2 and 4S2, each consumer product information display (CPID) enabling GUI of the illustrative embodiment is a new and independent Web browser having a Netscape-type framework, in which the six mode selection buttons 21A through 21G of the illustrative embodiment are displayed. When such CPID-enabling GUIs are displayed at the consumer's point of presence on the WWW, the consumer is free to select any one of the mode selection buttons and cause the system to enter the selected mode and precisely deliver the information service associated therewith without disturbing his or her present Cyberspace experience. The description of these modes will be described in detail hereinbelow with reference to FIGS. 2-1, 2-2, 2A and 2C.

Registration Solicitation Mode of the IPT Finding and Serving Subsystem

In the illustrative embodiments of the present invention, the data-synchronized IPD Servers of the system hereof 11 are also provided with an “Automated Registration Solicitation Mode” programmed by the webmaster (or administrator) of the IPI Web-site(s). In this mode, each IPD Server 11 analyzes the data collected within its Non-IPI Registrant Database. The data analysis procedure seeks to determine: (1) which “unregistered” products in the Non-IPI Registrant Database were the subject of an information request at the IPD Server; (2) how many hits (requests) were made for the product within a predetermined length of time (e.g. one week) by Internet users; and (3) whether the number of requests exceeds a particular “request threshold” (e.g. 100 requests in week period). Then for each unregistered product which has exceeded the request threshold, the IPD Server automatically sends an E-mail message to the associated company. Preferably, the E-mail message is designed to (i) inform the company of recent information requests for their products, and (ii) solicit the registration of such products with the IPD Server. Once registered with the system, such products can be easy found on the Internet by anyone wishing to use the product information finding techniques of the present invention.

Operation of the IPT Finding and Serving Subsystem and Method Hereof

When the Check Box button 21C is selected from the control frame 20B, the IPI Finding and Serving Subsystem enters its “UPN-Directed Information Access Mode” illustrated in FIG. 6C. Preferably, the user is provided with a choice of language (e.g. English, German, French, Japanese, Chinese, etc.) by way of an appropriate menu-selection screen. After the desired language selection is made, the home page is displayed upon the client subsystem's display screen. A typical display screen produced from the IPD Server might read as follows:

-   “Welcome to UPC-REQUEST™, the only Universal Product-Information     Finding and Serving System on the Internet. -   Have you purchased a particular product, are you considering the     purchase of a particular product, on which you would like current,     up-to-date information from the manufacturer or advertiser? -   Look no further than the UPC-REQUEST™ Universal Product-Information     Finding and Serving System.”

When the subsystem is in its “UPN-Directed Information Access Mode”, a Web-based information resource pertaining to any commercial product registered with the system can be displayed and selected by the user in order to automatically access the same from the Internet. Such information resources can include advertisements, specifications, operation descriptions, product simulations, purchase information, maintenance information, warranty and servicing information, product updates, distributor/reseller information, incentives (e.g. discounts, rebates, coupons, etc.), electronic data transaction screens, etc. In this mode, desired product information is obtained by simply entering the registered product's UPN (e.g. its UPC's 12 digit numerical string) into the Inout Box of the HTML form displayed in the information display frame 20C. Such data entry can be carried out manually using a keyboard data entry techniques, or automatically using a bar code symbol reader connected to the client subsystem as discussed in detail above. When using the seeded IPI Database described hereinabove, only the first six digits of the UPC number need be entered into the dialogue box. An exemplary display screen produced from the IPD Server might be as follows:

-   “Simply enter the 12 digit UPC the particular product; click     REQUEST, and then wait for the display of the list of Web locators     (URLs) at which the desired product information can be found on the     Internet?”

In response to such data entry operations, a list or menu of URLs organized according to information subfield classifications as set forth, for example, in FIG. 4A2, are displayed on client subsystem Ca making the request of the IPD Server 11. At this stage, another display screen associated with the HTML form produced from the IPD Server 11 would appear with an exemplary message as follows:

-   “Please select the URL from the displayed URL Menu using the     information subfield product information category displayed above.     This will connect you to the product information related to the     selected URL. You can return to the URL display list at anytime.”

Upon selecting a particular URL from the displayed URL menu, video and audio information content are automatically served from the IPI Server 12 hosting the selected URL and thereafter displayed on the client subsystem 13.

When the Check Box button 21D is selected, the IPI Finding and Searching Subsystem enters its Trademark-Directed Search Mode, illustrated in FIGS. 6D1 through 6D3. Preferably, the user is provided with a choice of language (e.g. English, German, French, Japanese, Chinese, etc.) by way of an appropriate menu-selection screen.

When the system is in its Trademark-Directed Search Mode, a predesignated information resource pertaining to any commercial product registered with the system can be automatically accessed from the Internet and displayed from the Internet browser of a client subsystem 13. Such information resources can include advertisements, specifications, operation descriptions, product simulations, product upgrade information, purchase information, maintenance information, warranty and servicing information, etc. In this mode, desired product information is obtained by simply entering the registered product's trademark(s) and/or associated company name into the Input Box of the HTML form displayed on the information display frame 20C of the client subsystem. An exemplary message associated with the HTML form produced from the IPD Server 11 might be as follows:

-   “Simply enter the trademark used in connection with the particular     product and/or the company name of the product's manufacturer; click     REQUEST, and then wait for the display of a list of Web locators     (URLs) at which desired types of product information can be found on     the Internet”

In response to such data entry operations, a list of URLs organized according to the information subfield classifications set forth in FIG. 4A2 are displayed on client subsystem placing the request. Upon selecting a particular URL from the displayed list thereof, video and audio information content are automatically served from the IPI Server hosting the selected URL and thereafter displayed on the client subsystem.

In an alternative embodiment of the present invention, the UPN-Directed Information Access Mode and the Trademark-Directed Search Mode can be integrated into a single server application so that there is no need or desire to manually select between mode activation buttons 21C and 21D, respectively. In such an embodiment, the interaction between the IPD Server and the requesting client subsystem can be designed to support the following Web server display screens and script underlying the same:

-   “Welcome to UPC-REQUEST™, the only Universal Product-Information     Finding and Serving System on the Internet. -   Have you purchased a particular product, or considering the purchase     of a particular product, on which you would like current, up-to-date     information from the manufacturer or advertiser? -   “Look no further than the UPC-REQUEST™ Universal Product Information     Finding and Serving System.” -   “Simply enter the 12 digit UPC number of the particular product,     click REQUEST, and select from the displayed menu of Web locators     (URLs) to find the desired product information on the WWW. -   “If you do not know the UPC number associated with the product you     are looking for, then simply enter the trademark used in connection     with the particular product and/or the company name of the     manufacturer, then click REQUEST, and wait for the display of the     list of Web locators (URLs) at which the desired product information     can be found. -   “Please select the URL from the displayed URL list by clicking on     it. This will connect you to the product information related to the     selected URL. You can return to the URL display list at anytime.”     Notably, such an integrated Web server application can be realized     in a variety of ways. The exact words and graphics used to create an     interactive script for an integrated Web server application will     vary from embodiment to embodiment of the present invention.

In instances when an IPI Website in accordance with the present invention is being served to consumers in retail environments using a computer-based kiosk as shown in FIG. 3A2, the consumer as well as retail sales clerk is presented with the option of ascertaining the price of an product in the store. This is achieved by simply depressing the “Price Display” button 21F on Control Strip 20B, shown in FIG. 3C, to engage the system in its price lookup/display mode. In this mode of operation, the consumer then need only scan the UPC bar code symbol on the product using bar code scanner 26 in order for the price to be looked-up in the Product Price Database maintained in the Retailer's Price Server (RPS) 35, and displayed on the kiosk display screen. In general, the Product Price Database of the hosting retailer can be made accessible by the computer-based kiosk in several possible ways. As shown in FIGS. 2-1 and 2-2, one way is to place the retailer's RPS on Internet (by using an HTTP server) and connect the RPS to the IPD Server 11 of the system by way of a CGI well known in the art. The CGI can be made accessible only by authorized client subsystems (e.g. computer-based kiosks installed in the hosting retailer's store and possibly administrators of the information delivery system). An alternative technique of connecting the Product Price Database to each computer-based kiosk would involve providing the RPS with a direct interface to each computer-based kiosk in the hosting retailer's store(s). This alternative technique may require the use of computer networking technology well known in the art.

A Best Mode Embodiment of IPT Finding and Serving Subsystem of the Present Invention

The IPI finding system (i.e. subsystem) of the present invention can be realized on the Internet in a variety of different ways. Each embodiment of the system will provide manufacturers, retailers, consumers and sponsors with various benefits hitherto unachievable using prior art systems and methodologies. A best mode embodiment of the system will now be described below with reference to Intent-to-Use (ITU) servicemarks that Assignee hereof has sought to register under the Lanham Act and ultimately use in reducing the Internet-based consumer product information finding system to commercial practice in the near future. The inventive subject matter herein disclosed can be readily applied to carry out such an Internet-based information finding and delivery system.

According to the best mode embodiment, the IPI Finding and Serving Subsystem 2, referred to hereinabove as the “UPC REQUEST™ Consumer Product Information Finding System” in FIGS. 7 and 8 hereof, comprises an integration of several subsystems including, for example: the UPC REQUEST™ Manufacturer/Product Registration Subsystem 33 (e.g. Web Document Server 30 and Workstation 31) including Web-based and Value Added Networks (VAN)-based infrastructure and processes 14 for supporting EDI and UPN/URL database management operations by manufacturers and/or their agents; the UPC REQUEST™ Database Management Subsystem 9 interfaced with the UPC REQUEST™ Manufacturer/Product Registration Subsystem 33; numerous UPC REQUEST™ kiosks (e.g. client subsystems 13) installed in retail stores, retail outlets and the like, each having a bar code symbol driven Internet browser providing access to the Internet through an Internet Service Provider (ISP); and all of the Web-enabled client subsystems 13 located in consumer homes, in consumer offices and on the road, having access to the Internet through an ISP. While distributed geographically, these subsystems are integrated through the infrastructure of the Internet.

The function of the UPC REQUEST™ Manufacturer/Product Registration Subsystem 33 is two-fold: (1) to enable qualified manufacturers to quickly and easily register their companies with the System (i.e. the UPC REQUEST™ Database Management Subsystem 9) by way of a Web-enabled computer system of their choice; and (2) to enable manufacturers and/or their agents to (i) easily link, manage and update their UPC numbers and linked URLs using any Web-enabled computer system 13 running the EDI (or XML/EDI) based UPN/URL Database Management software (downloaded during manufacturer registration), and periodically transmit such updated information to the UPC REQUEST™ Database Management Subsystem in order to update each manufacturer's information within the UPC REQUEST™ Database (i.e., IPI Database shown in FIGS. 4A1 and 4A2).

The function of the UPC REQUEST™ Database Management Subsystem 9 is to maintain and update the UPC REQUEST™ Database (shown in FIGS. 4A1, 4A2 and FIGS. 4C through 4C4), which contains various information items regarding registered manufacturers, service-subscribing retailers, and registered consumer products including, for example, UPC (and/or UPC/EAN) numbers assigned to consumer products and linked URLs pointing to published HTTP-encoded documents (i.e. Web pages) containing particular types of information related to such products.

Within the store of each retailer subscribing to the UPC REQUEST™ Consumer Information Service, the function of the UPC REQUEST™ kiosk is to provide consumer access to the UPC REQUEST™ Retailer Website (e.g. UPC REQUEST™ Retail @ Wal-Mart, UPC REQUEST™ Retail @ Home Depot, etc.). The UPC REQUEST™ Retailer Website served to both physical-kiosk and cyber-kiosks within the retailer's brick and mortar and EC stores, respectively, provides consumer access to UPN/URL information links relating only to those products old by the retailer and maintained within the UPC REQUEST™ Database Management System by the manufacturer or agent thereof. If desired by the subscribing retailer, its UPC REQUEST™ Retailer Website can be freely served to customers over the Internet, e.g. accessible from a hot-link embedded somewhere in the retailer's Web-site.

Within the realm of the UPC REQUEST™ System 2, the function of the Web-enabled client computer system 13 of each consumer, wherever it may be located (e.g. at home, in the office or on the road), is to provide consumer access the UPC REQUEST™ Central Website which is freely served over the Internet to any consumer having a Web-enabled computer system. Unlike each UPC REQUEST™ Retailer Website maintained by the UPC REQUEST™ Database Management System, the UPC REQUEST™ Central Website provides consumer access to UPN/URL information links relating to every product maintained within the UPC REQUEST™ Database Management System by every registered manufacturer. Any attempt by a consumer to access information from a particular UPC REQUESTS Retailer Website regarding a product not sold in the retailer's store will automatically result in a link over to the UPC REQUEST™ Central Website.

A Brief Description of the UPC REQUEST™ Information Service Suit

When installed in retail stores, the UPC REQUEST™ System provide will provide six revolutionary Internet-based consumer information services under the servicemarks HOME-PAGE™, INFO-LINK™, CYBER-SERVICE™, TRADE-MARK™, PRODUCT-TYPE™, and UPC-ENCODED-APPLET-DOWNLOAD™, respectively. Each of these information services is accessible to consumers and sales clerks alike from a UPC REQUEST™ Retailer Website (e.g. UPC REQUEST” @ Home Depot Website) accessed within a retail store, as well as from on the UPC REQUEST™ Central Website.

In the UPC REQUEST™ version of the IPI Finding and Serving Subsystem of the present invention, the INF-LINK™ provision is supported during and enabled by Manufacturer/Product Registration Mode; the HOME-PAGE™ provision is supported during and enabled by the Manufacturer Website Search Mode; the CYBER-SERVICE™ provision is supported during and enabled by UPN-Directed Information Access Mode; TRADE-MARK™ provision is supported during and enabled by the Trademark-Directed Search Mode; PRODUCT-TYPE™ provision is supported during and enabled by the Product-Description Directed Search Mode; and UPC-ENCODED-APPLET-TAG-DOWNLOAD/DISTRIBUTE™, provision is supported during and enabled by the UPC-Encoded Applet Tag Download/Distribution Mode. Each of these system modes have been described in great detail hereinabove.

To constantly remind the public at large of the “fee-paying” sponsors of the UPC REQUEST™ System, all Web pages displayed by the UPC REQUEST™ System in a retail store (e.g. on UPC REQUEST™ @ Home Depot Website), or on the UPC REQUEST™ Central Website, will be displayed within a three-frame display “framework” comprising a sponsor frame, a control frame, and an information frame.

The “sponsor frame”, located on the upper-most portion of the Internet browser screen, displays the sponsor's greeting such as, for example, “Welcome to UPC REQUEST, sponsored by Visa and Federal Express.”

The “control frame”, located on the left-most side of the Internet browser screen, will provide six mode activation buttons. The first mode activation button 21A enables consumers to request the INFO-LINK™ service. The second mode activation button 21B enables consumers to request the HOME-PAGE™ service. The third mode activation button 21C enables consumers to request CYBER-SERVICE. The fourth mode activation button 21D enables consumers to request TRADE-MARK™. The fifth mode activation button 21E enables consumers to request PRODUCT-TYPE™. The sixth mode activation button 21F enables consumers to request UPC-ENCODED-APPLET-DOWNLOAD/DISTRIBUT™. A seventh button 21G enables the download a free plug-in software module which automatically installs a “Product Information” button on the graphical user interface of the consumer's Internet browser, so that the UPC REQUEST™ Central Website can be accessed anywhere in the world with a single click of the mouse button.

The “information frame”, occupying the balance of the Internet browser screen, will display: all HTTP (i.e. Web) and FTP pages launched by in-store scanning of UPC-labeled products during HOME-PAGE™ or CYBER-SERVICE™; all HTTP and FTP pages launched by clicking on hypertext-links embedded within Web pages accessed through a particular UPC REQUEST™ Retailer Website in retail stores or from the UPC REQUEST™ Central Website; as well as all information search and display (menu) screens served by a UPC REQUEST™ Retailer Website to the UPC REQUEST™ Central Website.

In retail stores subscribing to the UPC REQUEST™ System, HOMEPAGE™ manufacturer's Website search site will enable consumers to automatically access the WWW Home Page of any registered manufacturer by scanning the UPC (or UPC/EAN) bar code symbol on any product thereof using the bar code symbol reader associated with a UPC REQUEST™ kiosk. In general, the UPC REQUEST™ kiosk can be realized by any Web-enabled computer system 13 having an Internet browser program, on-line access to the UPC REQUEST™ Retailer Website, and optionally a touch-screen display panel. The UPC REQUEST™ kiosk may, however, be realized as an inexpensive Internet access terminal comprising a Web-enabled network computer (NC), an LCD touch-screen panel, and a laser scanning bar code symbol reader integrated within an ultra-compact housing that is mountable within diverse locations within retail stores. As shown in FIG. 3A5, the UPC REQUEST™ kiosk may also be integrated within a conventional Point of Sale (POS) station having a laser scanning bar code symbol reader and a large rotatable LCD display panel. Being as easy to install as a telephone modem, UPC REQUEST™ kiosks of this design can be widely deployed throughout retail stores world-wide with minimal modifications to the preexisting information infrastructure. At home, in the office, or on the road, HOME-PAGE™ enables consumers to automatically access the WWW Home Page of any registered manufacturer by entering the UPN (or UPC/EAN number) on any product into the search screen served up by a particular UPC REQUEST™ Retailer Website, or by the UPC REQUEST™ Central Website.

INFO-LINK™, carried out using EDI (or XML/EDI) based UPN/URL Database Management software (downloaded from Manufacturer/Product Registration Subsystem 33), enables manufacturers to simply relate (link), manage and update therein (i) the UPN (or UPC/EAN number) on any product with (ii) the Internet address (i.e. URL) of product-related Web pages published on the Internet by the manufacturer, its agents, or others, for subsequent access and display by consumers using CYBER-SERVICE™. While the INFO-LINK™ service would be made accessible through UPC REQUEST™ kiosks 13 in retail stores (i.e. for the sake of vendors who frequent the same), the actual UPN/URL information linking and management operations associated with the INFO-LINK™ service will typically occur in the “back-offices” of registered manufacturers using Internet-enabled computer systems accessing INFO-LINK™ through a hot-linked URL posted on the UPC REQUEST™ Retailer Website and/or the UPC REQUEST™ Central Website. UPC-ENCODED-APPLET-DOWNLOAD™, carried out using EDI (or XML/EDI) based processes, enables manufacturers (via the system administrator) to distribute CPIR-enabling Applets/Servlets to retailers, manufacturers, advertisers and others about the globe so that they may embed the same within HTML-encoded documents in order that consumers can instantly initiate UPN-directed searches within the centralized UPN/URL Database Management Subsystem 9 hereof and display the search results within a CPID-enabling Java GUI which performs the function of a “cyber-kiosk” provided at the consumer's point of presence on the WWW.

CYBER-SERVICE™, accessible through a particular UPC REQUEST™ Retail Website or the UPC REQUEST™ Central Website, enables consumers at home, in the office, on the road, and in retail stores, to quickly access particular types of product-related information which have been published on the WWW by registered manufacturers, their agents and others about consumer products registered with the UPC REQUEST™ Database Management System. CYBER-SERVICE™ displays such product-related information in a menu-like format organized by particular information types (e.g., Product Advertisements, Product Endorsements, Product Reviews, Product Rebates and Incentives, Product Description, Product Manual/Instructions, Product Updates (at FTP Sites), Product Returns, Warranty and Repair Service, Direct Product Purchase, Retailers, Wholesalers, Complementary Products, Company Annual Report, Stock Purchase, etc.). Each displayed information menu associated with a consumer product contains hyper-linked URLs pointing to HTML-documents containing particular types of product-related information linked to the product by the manufacturer or its agent.

When CYBER-SERVICE™ is selected from a particular UPC REQUEST™ Retail Website, each product-related Web page listed in the displayed “information menu” can be accessed and displayed simply by touching the corresponding Internet address (i.e. URL) displayed on the touch-screen display panel of the UPC REQUEST™ kiosk in the retail store. When CYBER-SERVICE™ is selected from the UPC REQUEST™ Central Website, each product-related Web page listed in the displayed “information menu” can be accessed and displayed simply by clicking the display screen thereof accessed by an Internet-enabled computer system.

TRADE-MARK™, accessible through a particular UPC REQUEST™ Retail Website or the UPC REQUEST™ Central Website, enables consumers to quickly access particular types of product-related information from the UPC REQUEST™ Database, by using the trademark or tradename of the related product. When this mode of service is requested, a search screen is displayed within the information frame so that the consumer or sales clerk can enter the trademark or tradename for the related consumer product.

PRODUCT-TYPE™, accessible through a particular UPC REQUEST™ Retail Website or the UPC REQUEST™ Central Website, enables consumers to quickly access particular types of product-related information from the UPC REQUEST™ Database, by using a descriptive term for the related product. When this mode of service is requested, a search screen is displayed within the information frame so that the consumer or sales clerk can enter a descriptive term for the related consumer product. To maximize value to a particular retail store's customers, each UPC REQUEST™ Retail Website served at each retail store subscriber would be made accessible to consumers outside their retail stores (e.g. at home, in the office or on the road) by several Internet access methods including, for example: through a hot-linked URL posted on the retail store's Website, pointing to the UPC REQUEST™ Retail Website; through a publicly accessible URL, e.g. http://www.upcrequest.com/ @ retail store; etc.

Benefits Provided to Sponsors Promoting the UPC REQUEST™ System

HOME-PAGE™ and CYBER-SERVICE™ will foster customer loyalty and patronage with sponsors by providing consumers with valuable product-related information before and after product purchases.

CYBER-SERVICE™ will provide sponsors with an economical and effective way of marketing products and services to their customers and shoppers worldwide.

HOME-PAGE™ will provide sponsors with valuable advertising space on the UPC REQUEST™ Central Website, for subleasing to retailers, manufacturers and business concerns.

INFO-LINK™ and UPC-ENCODED-APPLET-DOWNLOAD/DISTRIBUTE™ will provide sponsors with an effective way of promoting their products and/or services among manufacturers, retailers and consumers using the UPC REQUEST™ System.

Benefits Provided to Customers Using the UPC REQUEST™ System in Retail Stores

HOME-PAGE™ will allow customers to automatically access Home Page of any manufacturer's Website by simply scanning the UPC bar code symbol on any product thereof at any UPC REQUEST™ information kiosk in a retailer's store.

CYBER-SERVICE™ will allow customers to quickly access (by touch-screen URL selection) particular types of product-related information that have been published on the World Wide Web (WWW) by manufacturers, their agents or others, and registered within the UPC REQUEST™ Database through INFO-LINK™.

TRADE-MARK™ will allow customers to quickly access product related information menus from the UPC REQUEST™ Database using trademarks or tradenames used in connection with the product on which information is being sought.

PRODUCT-TYPE™ will allow customers to quickly access product related information menus from the UPC REQUEST™ Database using descriptive terms related to the product on which information is being sought.

Benefits Provided to Customer Using the UPC REQUEST™ System at Home in the Office or on the Road

HOME-PAGE™ will allow customers to automatically access the Home Page of any manufacturer's Website by simply entering the UPC (or UPC/EAN) number on any consumer product, into a UPC REQUEST™ search screen served from the UPC REQUEST™ Central Website and accessible to anyone using an Internet-enabled computer system at home, in the office, or on the road.

CYBER-SERVICE™ will allow customers to quickly access from the UPC REQUEST™ Database, particular types of product-related information that have been published on the WWW by manufacturers, their agents or others, and registered within the UPC REQUEST™ Database through the INFO-LINK™ service.

TRADE-MARK™ will allow customers to quickly access product related information menus from the UPC REQUEST™ Database using trademarks or tradenames used in connection with the product on which information is being sought.

PRODUCT-TYPE™ will allow customers to quickly access product related information menus from the UPC REQUEST™ Database using descriptive terms related to the product on which information is being sought.

Benefits Provided to Retailers Providing UPC REQUEST™ System in Their Stores

HOME-PAGE™ and CYBER-SERVICE™ will foster customer loyalty and patronage with retailers by providing shoppers with valuable product-related information before and after product purchases.

CYBER-SERVICE™ will provide retailers with an economical and effective way of marketing its products to customers and shoppers within its stores.

CYBER-SERVICE™ will provide retail sales personnel with an opportunity to learn about a retailer's products by scanning the UPC bar code symbols on such products, and selecting product-related Web pages for in-store review and sales-training sessions whenever customer demand allows.

HOME-PAGE™ and CYBER-SERVICE™ will provide retailers with valuable advertising space in their stores for subleasing to manufacturers and others (e.g. local sponsors) in order to self-finance the store-wide delivery of the UPC REQUEST™ Service.

TRADE-MARK™ will allow sales clerks and customers to quickly access product related information menus from the UPC REQUEST™ Database using trademarks or tradenames used in connection with the product on which information is being sought.

PRODUCT-TYPE™ will allow sales clerks and customers to quickly access product related information menus from the UPC REQUEST™ Database using descriptive terms related to the product on which information is being sought.

Proposed Revenue Model for the UPC REQUEST™ System

The UPC REQUEST™ System will generate revenue from at least four sources: Manufacturer Fees paid by manufacturers who want to register their products and product-related Web pages with the UPC REQUEST™ Database; Retailer Fees paid by retailers who want to provide bar code driven access to the UPC REQUEST™ System in retail stores; Sponsor Fees paid by Sponsors of the UPC REQUEST™ System; and Advertiser Fees paid by advertisers on the UPC REQUEST™ Central Website.

Manufacturers desiring to register their consumer products and product-related Web pages within the UPC REQUEST™ Database would pay a one-time Manufacture Registration Fee, based on volume of sales. An annual maintenance fee may be desired or necessary. Minimally, such fees should cover the cost of the EDI and UPN/URL Database Management software (and updates) automatically downloaded to each manufacturer upon registration. Such Web-based EDI software enables manufacturers to easily manage the UPC numbers and Web page URLs associated with their changing product lines, and automatically transmit such information to the UPC REQUEST™ Manufacturer/Product Registration Subsystem in order that the UPC REQUEST™ Database Management Subsystem is periodically updated.

Retailers providing bar code driven access to the UPC REQUEST™ System in their retail stores would pay an annual Retailer License Fee based on the number of UPC REQUEST™ kiosks deployed therein (within store isles, at POS stations and behind information/service counters).

Each sponsor of the UPC REQUEST™ System would pay an annual Sponsor Fee for the right to display its name, trademark/servicemark and/or message in hypertext within a selected portion of the sponsor frame displayed by licensed UPC REQUEST™ kiosks in retail stores, as well as Internet-enabled computer systems accessing the UPC REQUEST™ Central Website. For marketing reasons, it would be desirable to limit the number of sponsors of the UPC REQUEST™ System at any instant in time.

Advertisers, who advertise on the UPC REQUEST™ Central Website, would pay an Advertiser Fee based on the time and location that the Web advertisement is displayed.

Usage of the UPC REQUEST™ in Diverse Retail Markets

The UPC REQUEST™ System can be used to provide consumers quick access to useful product-related information in diverse types of retail shopping environments including, for example, retail superstores, discount department stores, home-improvement stores, computer superstores, drugstores and pharmacies, music stores, video rental stores, bookstores, supermarkets, grocery stores and the like. Each of these retail markets provides a unique environment in which the UPC REQUEST™ System can be used by manufacturers of consumer products to effectively deliver product-related information to consumers in retail stores, at home, in the office or on the road, before and after consumer purchases.

As the UPC REQUEST™ System provides manufacturers with an effective way and means of making direct contact with present and future customers, it enables both manufacturers and retailers alike to influence demand in ways that have hitherto have been unavailable. Such features of the UPC REQUEST™ System present enormous growth opportunities in retail supply and demand chain management across diverse markets within our ever expanding global economy.

Modifications of the Illustrative Embodiments of the Invention

The present invention has been described in great detail with reference to the above illustrative embodiments. It is understood, however, that numerous modifications will readily occur to those with ordinary skill in the art having had the benefit of reading the present disclosure.

For example, in the illustrative embodiments described hereinabove, separate databases are maintained by each data-synchronized IPD Server for (i) registered products within the system, and (ii) non-registered products within the system. Notably, the reasons for using a dual database design of this sort would be based largely on economics, namely: only those companies who have paid the required maintenance (or registration) fees get their products and linked-URLs “registered” with the system, whereas non-paying companies and organizations do not get their products and linked-URLs registered with the system, regardless of how such product-URL information is ascertained (e.g. by solicitation versus data-mining).

Thus it is contemplated that in some embodiments of the present invention, each IPD Server will be designed to maintain only a single database for maintaining product-URL information currently available on the Internet. In such embodiments of the present invention, the concept of “non-registered” products will be altogether avoided, since the system implementation and administration may be designed not to require companies to pay maintenance (or registration) fees in order that their products and linked URLs are registered with the IPI system. Instead, some alternative income producing scheme will be used in such embodiments of the present invention (e.g. user fees, subscription fees, Internet browser-licensing fees, etc.) for system maintenance and administration.

When practicing the system and method of the present invention, it is preferred that the UPC label (with its human-readable UPC number) assigned to the particular product be attached, embossed or otherwise embodied on an accessible surface thereof. In addition to applying the UPC label to the external packaging of the product, it is preferred that the UPC label also be printed on any and all product instructions and manuals provided with the product. In this way, the UPC number can be easily read by a human being and then used to access a desired type of product information using the system and method of the present invention.

In order that the system hereof can be used to find information pertaining to large products such as automobiles, motorcycles, skidoos, farm machinery, boats, etc., the present invention also contemplates assigning UPNs (e.g. UPC or EAN numbers) to such products and attaching, embossing or otherwise embodying the same on an accessible surface thereof. Also, the UPN label can be printed on all instruction booklets and/or operating manuals normally provided with the product. In this way, information related to any particular product that is posted anywhere on the Internet and linked to URLs registered with the IPD Servers 11 of the system hereof can be readily found using the uniquely assigned UPC number assigned thereto by the manufacturer at the time of sale. Notably, multimedia information about such products can be most helpful in regard to the operation, repair and servicing of such products.

The system and method of the present invention has been shown to combine the use of UPNs, trademarks and company names when making a product information request of the system. It is understood, however, that the present invention can be practiced using any one of these items of information, alone or in combination with each other, in order to place a product information request with the system hereof.

Also, while the system of the illustrative embodiment has been shown used to collect, transport and serve information related to consumer products, it is understood that the system can be used to link the URLs of HTML (and other Internet) documents with consumer services assigned uniform service numbers (USN) which may be based on the UPC or EAN numbering system, or some other suitable system. In such alternative embodiments, the IPI Database would contain information pertaining to uniform service numbers (USN) that have been linked to the URLs of HTML or like documents on the Internet by the manufacturer or its agents, in essentially the same manner as conducted for consumer products. Such USN/URL management operations can be carried out in a similar to that described in connection with UPN/URL management along the retail supply and demand chain.

In connection with the consumer service information embodiment of the present invention, it is understood that at present, few (if any) services have been assigned a UPC (or EAN) number in the manner that nearly all consumer products have been assigned in the contemporary period. In spite of this fact, however, the present invention contemplates the need and utility of widespread assignment of UPC, EAN or similar numbers by service providers to particular services (as well as the imprinting of UPC, EAN or similar symbols on printed service brochures and advertisements. Notably, assigning uniform service numbers (USNs) to particular services, and labeling printed and graphical brochures and advertisements with such universal numbers, will provide a number of new opportunities hitherto unavailable.

In particular, service-related information could be easily found (i.e. located and accessed) on Web-sites using the system and method of the present invention, and thereafter the service easily procured through an electronic data transaction. In accordance with the present invention, this can be achieved by uniquely identifying and assigning “particular” services by a Universal Service Code (USC) which has many if not all of the attributes of a conventional UPC. While not necessary, a single digit may be optionally added to the USC in order to demark that services, rather than products, are being identified. An example of such USC labeling would be printing an assigned UPC label (number) on: admission tickets to a theatrical, dramatic or musical performance and/or its playbill; admission tickets to a movie; admission tickets to a concert and/or its concert program; admission tickets to a sporting event and/or its sports program; admission tickets to an art, science or history museum; admission tickets to the zoo or botanical gardens; and the like. The UPC label would be encoded to identify a particular event at which an entertainment, educational or professional service is provided. The UPC label printed on the tangible medium associated with the promotion of or access to the particular service would then be registered with the IPSI Registrant Database of the system hereof, along with the name of the provider of the service, and a list of URLs that identify the Web locations at which particular kinds of information related to the particular service can be found (in accordance with the categories of FIG. 4A2).

These and all other such modifications and variations are deemed to be within the scope and spirit of the present invention as defined by the accompanying Claims to Invention. 

1. A consumer product information catalog system for operation on the World Wide Web (WWW), said consumer product information catalog system comprising; a database management subsystem including a relational database containing (i) a plurality of Universal Product Numbers (UPNs) uniquely associated with a plurality of consumer products offered for sale in a stream of commerce, and (ii) a plurality of categorized Uniform Resource Locators (URLs) symbolically linked to each one of said plurality of UPNs, wherein each said categorized UPN points to a consumer product related information resource published on the World Wide Web (WWW) supported by the infrastructure of the Internet; said database management subsystem providing means for manufacturers and/or their agents to dynamically update said relational database, a Consumer Product Information Request (CPIR) enabling servlet tag containing information related to the location of a computer executable servlet; a first Internet information server for publishing a library of the CPIR-enabling Servlet tags on the Internet, said first Internet information server with means for providing to a user's browser, HTML-encoded documents publishable on the WWW with at least one of the CPIR enabling Servlet tags embedded within one of said HTML-encoded documents; a second Internet information server operably connected to said database management subsystem and the infrastructure of the Internet, with means for detecting when at least one of said CPIR-enabling Servlet tags embedded in one of said HTML-encoded documents has been selected, and means for activating said computer executable servlet; wherein said means for activating activates said computer executable servlet, automatically executing a method comprising: loading and running classes so as to perform a UPN-directed search on said database management subsystem, conducting a UPN-directed search carried out within said database management subsystem, and displaying within an Internet-enabled browser, program results from said UPN-directed search, said displaying including a GUI in the form of a menu of categorized URLs pointing to consumer product related information resources published on said WWW and symbolically linked to the UPN corresponding to the selected CPIR-enabling Servlet tag, and said results including a menu of categorized URLs pointing to consumer product related information resources.
 2. The consumer product information catalog system of claim 1, which further comprises: license-related information specifying the terms and conditions of use of the system and the conditions under which said computer executable servlet shall operate on domains of the Internet.
 3. The consumer product information catalog system of claim 1, wherein said first Internet information server is a Java-enabled information server.
 4. The consumer product information catalog system of claim 1, wherein said first Internet information server is an HTTP-type information server.
 5. The consumer product information catalog system of claim 1, wherein said first Internet information server is implemented on a first computing system, and said second Internet information server is implemented on a second computing system.
 6. The consumer product information catalog system of claim 1, wherein said classes and said method are expressed in the Java programming language.
 7. The consumer product information catalog system of claim 1, wherein said GUI is implemented as a Web-based GUI.
 8. The consumer product information catalog system of claim 1, wherein said GUI is implemented as a Java-based GUI.
 9. The consumer product information catalog system of claim 1, wherein said HTML-encoded document contains a graphical image of the consumer product uniquely associated with the UPN corresponding to the selected CPIR-enabling Servlet tag.
 10. The consumer product information catalog system of claim 1, wherein the consumer selects said CPIR-enabling Servlet tag by performing a mouse-clicking operation.
 11. The consumer product information catalog system claim 1, wherein said second Internet information server is an HTTP-type information server. 